Start Profiling ASP.NET

An ASP.NET application can be profiled using the development web server (WebDev.WebServer) or the Internet Information Services web server. It is recommended that the development server be used, if possible, since using that server will not affect any other ASP.NET applications.

To profile the memory of an ASP.NET process, perform the following steps.

1.   Select the Profile ASP.NET command from the menu or toolbar.

2.   The “Profile ASP.NET” wizard appears.

3.   Select how the ASP.NET application should be launched:

•      Launch using WebDev.WebServer (recommended)

•      Launch using Internet Information Services

4.   If the development web server is used, use the Browse button or the Web-site directory drop-down list to define the directory where the web site is located.

5.   In order to automatically start the ASP.NET application, you can select a web page that should be requested when the profiling is started. If you do not want a page to be selected, select (none) in the request page drop-down list.

6.   Select the command Start.

If the IIS server is used, this will stop the IIS Services (“IIS Admin,” “World Wide Web Publishing,” and any other services that depend on “IIS Admin”). A number of environment variables are set, and then the stopped services are restarted.
If the development server is used, a new instance of WebDev.WebServer will be started.

7.   If you want to profile using the default settings, click Start to start the application.

8.   If you want to modify settings, you can use the Next button to modify some common settings.

9.   When you have decided on the settings, click Start to start the application.

10. If you did not define a page to request, you need to force the start of the ASP.NET process by requesting an ASP.NET page (e.g., an .aspx page) when you get the “Waiting for profiled process to start” message.

11. When the “Waiting for profiled process to start” message has disappeared, you can start collecting heap snapshots.