vs2015/2013/2012 IIS Express Debug Classic ASP

Resources:

https://msdn.microsoft.com/en-us/library/ms241740 (v=vs.100). aspx

When you attach to a ASP Web application, make sure you select the appropriate program types in the attach to Process dialog box. When you debug script, Managed code must isn't be selected.

http://weblogs.asp.net/akjoshi/Debugging-classic-asp-application-with-Visual-Studio-2005

http://weblogs.asp.net/dixin/debugging-classic-asp-with-visual-studio-2013

http://stackoverflow.com/questions/4520960/does-iis-express-support-debugging-classic-asp/27948911#27948911

http://stackoverflow.com/questions/19760878/ Application-debugging-is-disabled-in-visual-studio-2012-on-classic-asp-debugging

1. If you press F5 to start debugging in VS, the default is Managed code. It is not possible to debug ASP pages.

2. First, modify the C:\Users\dotd\Documents\IISExpress\config\applicationhost.config and modify the <asp> section to read as follows:

<asp scripterrorsenttobrowser= "true" enableparentpaths= "true" bufferingon= "true" errorstontlog= "true" Appallowdebugging= "true" appallowclientdebug= "true" >        <cache disktemplatecachedirectory= "%temp%\ iisexpress\asp Compiled Templates "/>        <session allowsessionstate=" True "/> <limits        /></asp >

3. Start IIS Express in CMD using the following command

Iisexpress/config:c:\users\dotd\documents\iisexpress\config\applicationhost.config/site:aspdemo

4. In VS with "attach to process" process attached to Iisexpress.exe, note the "Attach to" option to select "Script" (because it is ASP) instead of "managed" (This is ASP.) NET is the default way).

5. First access the page you want to debug in the browser (this step is important and is the basis for the next steps).

6. If you do the 5th step, in VS, "Solution Explorer" you should see a scenario similar to the following

7. OK, now open the hello.asp (instead of the local directory's hello.asp) break point under Script document. (See that "dynamic", which means you hit the breakpoint to be debugger know).

8. Revisit the page and hit the breakpoint.

vs2015/2013/2012 IIS Express Debug Classic ASP