StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<blockquote> <p>Although the primary focus of Web debugging in Visual Studio 2010 is ASP.NET, you can also debug legacy ASP Web applications.</p> <p>ASP code executes in the Internet Information Services (IIS) process (in-process execution) or in a separate Mtx.exe process (out-of-process execution). To debug ASP code, you must attach to the IIS or Mtx.exe process. To debug client-side script as well, you must also attach to the IIS process. For information on how to attach to processes, see Attaching to Running Processes.</p> <p>When you attach to an 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 not be selected. You cannot debug script and managed code at the same time in Visual Studio 2005.</p> </blockquote> <p>and</p> <p><a href="http://msdn.microsoft.com/en-us/library/3s68z0b3.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/3s68z0b3.aspx</a></p> <blockquote> <p>To attach to a running process</p> <ul> <li><p>On the Debug menu, select Attach to Process. If no project is open, select Attach to Process on the Tools menu.</p></li> <li><p>In the Attach to Process dialog box, find the program that you want to attach to from the Available Processes list.</p></li> <li><p>In the Attach to box, make sure that the type of code you will debug is listed. The default Automatic setting tries to determine what type of code you want to debug. If the automatic setting is not appropriate:</p></li> <li><p>Click Select.</p></li> <li><p>In the Select Code Type dialog box, click Debug these code types and select the types to debug.</p></li> <li><p>Click OK.</p></li> <li><p>Click Attach.</p></li> </ul> </blockquote>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload