Search Wiki:

Server Notes

• Microsoft Visual Studio AJAX Profiling Extensions is written in 100% managed code, so processing web sites/applications/pages through the IIS7 integrated pipeline is required. Only sites and applications that are associated with an “integrated mode” Application Pool can be profiled.

• An Http handler is installed for the site you selected in setup. This allows all requests from the web site that are running in an integrated Application Pool to be seen by the AJAX Profiling Extensions. After install the “Add profiling code to outgoing JavaScript” option is on, so all pages containing JavaScript in the site you selected will be modified for profiling.

• All data files are stored in the CommonAppData location for your operation system ( \ProgramData\Microsoft\Visual Studio\AJAX Profiling Extensions on Vista and later). A directory is created for each profiling session and a private web.config file holds the current Profiling Extensions settings. The data directories will remain even after an uninstall

• There is a known incompatibility with the way Profiling Extensions captures output and the WebResource.axd handler. Our handler is unable to capture the output from pages generated by this handler, and so all output is served to the client unchanged. The purpose of the handler is to take data from a managed assemblies resources, and serve it up on the web. Most often, it is used for images and CSS, neither of which we instrument.

• All profiling options available in the admin console can be set by directly modifying the private web.config XML file
If there are some URLs you do not want to have modified in your selected site, either run that application under the classic application pool, or add it to the web.config <ignoreUrls> section. By default there is an entry <add url="WebResource.axd" /> to ignore any page generated by the Web resource handler. If any substring of the full URL matches a string in the <ignoreUrls> section, that page will not be modified for profiling.

• JavaScript blocks are identified by computing a hash function from all the text in the JavaScript block. If there is more than one identical JavaScript block in a profiling session, all profiling will be attributed to the first location where that block of script is found.

• Due to security built into browsers that prohibit cross-site scripting, profiling data can only be posted back to the originating site on the server. Because of this profiling data can only be recorded for sites on the server that have Ajax Profiling Extension server components installed. There are two command files that can be used to add and remove additional sites on your web server for profiling:
addSite.cmd “my site name” will add profiling components to a site.
removeSite.cmd “my site name” will remove the components from a site.
These command files can be found in the install directory for the server components (default: c:\program files\Microsoft Visual Studio\Ajax Profiling Extensions\)
When the setup program is used to uninstall server components, it will not only remove the components from the site selected during setup but also all sites added with the “addSite.cmd” command file.
Last edited Apr 21 2009 at 6:15 PM  by AdamE, version 1
Page view tracker