I'm searching for a free ASP.NET profiler, and I stumbled upon EQATEC Profiler for .NET, but I can't find any instructions on how to profile ASP.NET projects with it. Please post step-by-step instructions or a link with sufficient info.
I'm using Visual Studio 2008 Professional and .NET 3.5.
It looks like they have changed their user interface since Pavel's instructions were posted. Here are the instructions I wrote up for my team. They replace steps 4-8 in Pavel's post.
To profile an ASP.NET application using EQATEC, just select the application’s bin folder in the App Path setting.
Then, click the Build button at the bottom of the form.
Then, load your app and go to the page you want to profile. Go to the Run tab and click the Reset Counters button.
Then, do the action that you want to profile. When it’s done, click the Take Snapshot button.
When that is done, a snapshot report will appear in the bottom list. You can double-click on it to view it.
This should work for ASP.NET web projects:
Compile your project.
Start web application. You can right-click on some .aspx file in Visual Studio and select "View in Browser". (If you start your application later you risk overwriting profiled DLL.)
Start EQATEC Profiler.
On the Build tab browse to bin folder of your project.
Click “App options” button
Set output folder to $(AppDir) only.
Uncheck “Ordinary app”.
Click Build button.
Switch to your favourite browser. Navigate to the page you want to profile. You should get "Profiled app started" entry in Run tab in EQATEC Profiler.
Click "Take snapshot" button. A new entry should appear in "View snapshot reports" list. Select it and click View button.
Edit: Updated instructions according to comment.
From the EQATEC forums:
ASP.NET?
tracing asp.net web application
Profiling web application
You may need to get a compiled version of your site (is there a dll for the site in the bin folder or just the dependencies?).
The easiest way to do this is to publish it. (Just right hand click the site in Visual Studio). Then Pavel's answer will work just fine.
Related
I am using VS 2019 and web app is asp.net. I have signed into my Azure/Microsoft account through VS. When I tried to publish the app, I got the screenshot below. Somehow the "Next" button is greyed out so I cannot move forward to create my publish profile. By the way, I am learning Azure and using the free App Service Plan now.
You need to create App Service：
see: Publish your web app.
Here is what happened. To associate with Azure, a Microsoft account is linked to an Azure Directory. When I sign into Visual Studio with the Microsoft Account, the link is supposed to established automatically. But somehow it was not for my case. In Visual Studio, open "Personalization Account" page, click "Apply Filter" link, the next scene is where I can select which directory to be linked. I had only one directory but somehow it was not checked. Once I checked it, I am able to publish.
I have developed an ASP.NET Web Forms Application in Visual Studio 2017(CE). It's the project that I've developed for my college, as an objective to run it as an Intranet Application so that it could run on a IIS on a PC and people can access it over the Intranet. I've tried using the Web Deploy method, generated a Folder and addressed the IIS to the Published files of Visual Studio. But I don't get it to work, and I feel it's not the right way.
I've tried some research but haven't been able to figure out the right context. Can anyone please recommend me the right place of instructions? Or instruct here itself?
Go to Solution Explorer and select the project then right-click the project
Click the Publish menu item then left panel to publish screen will be open like below screen
Select the publish option as IIS, FTP, etc then click to publish button
The publish window will be open then select publish method as File System and type the Target location as http://localhost/Appname and click Next button.
Now, you can see the setting and file publishing options whatever you want to configure the options and click the Save button
Now you can find the application was published URL http://localhost/App in the output window
I have Web Application which I would like to deploy to my web server. I do not want to use Windows Azure, I have my own server. I even do not have my profile to publish to Azure. I believe it is OK to not have the profile and continue using VS2012. I would like have complied binary files and all my pages (master, aspx) together with my controls (ascx), js, css files and without code-behind files placed in my local folder. Then I plan to pack them and copy to my server through FTP. Sounds trivial. But...
When I hit right click over my Web Application project and then "Publish...", I have Publish Web window. The first step asks me if I want to publish to Windows Azure. In this case I have to provide my profile which I do not have. I do not need it. I just want to deploy to my local folder all except code-behind files. I cannot choose the next step which is "Connection". So I hit "Publish" button. And now, now I am stuck, because I have to provide my profile (see attached screenshot). Could you tell me how I can prepare my web application for deployment to my web server? Thank you.
If you are not planning on using Azure, simply ignore the statement at the top of that screen, it is only helpful if you are publishing to Azure.
To get past this step, click on the drop down and then click "New profile".
After that you will be taken through the rest of the wizard were you can setup your connection details etc.
Is there any way to protect the code written in the cs files? Also for the database?
We designed a website and we're considering publishing it and we have to deliver the project as a college project, but we want to protect the code so we can secure it in case we publish it.
We are already considering publishing the site and then giving them its url but it's our last option.
What can we do in this case besides publishing the site?
Thanks :)
To compile your project into a single dll file, you have to use the Publish Web Site function of Visual Studio. I use Visual Studio Express 2012 (version 11), so if you don't have this version, then there could be slight differences.
Click on the "BUILD" menu, then select Publish Web Site
Create a new Profile if you haven't done so.
Click on 'Connection' on the left side menu of the window, and choose File System to save it on a folder on your computer
Click 'Settings'. Open up File Publish Options and select the following:
Click on the 'Configure' link of the second option in the above screenshot. This will open the following window. Here you can play around with the merge settings. I've tried the 3rd and last option on a test website, and the output was similar. The text (testwebsite) in the textbox is for the name of the DLL file.
Click 'Publish'
I'm developing on a site with a few hundred user controls. When debugging the web app (pressing F5 in Visual Studio 2008), it takes quite some time to compile it and start Cassini. I've noticed that every user control is compiled to a separate dll in temporary asp.net-files and it takes quite a lot of time.
Is it possible to speed up this process, possibly by compiling to just one dll, and still be able to debug the web application?
This is from the article:
http://weblogs.asp.net/scottgu/archive/2006/09/22/Tip_2F00_Trick_3A00_-Optimizing-ASP.NET-2.0-Web-Project-Build-Performance-with-VS-2005.aspx
Enable the on-demand compilation option for your web-site projects. To enable this, right-click on your web-site project and pull up the project properties page. Click the "Build" tab on the left to pull up its build settings. Within the "Build" tab settings page change the F5 Start Action from "Build Web Site" to either the "Build Page" or "No Build" option. Then make sure to uncheck the "Build Web site as part of solution" checkbox:
Have you considered moving to a web application project? That will compile all of your code into one dll, but this could be a big change. I would try changing the start options first.
A few tips in here, which helped (batch="false" in web.config and moving the temp-files to a ram-disk):
http://blog.lavablast.com/post/2010/12/01/Slash-your-ASPNET-compileload-time.aspx
Also, consider building in parallel:
http://www.hanselman.com/blog/HackParallelMSBuildsFromWithinTheVisualStudioIDE.aspx