Edit Question - KnowledgeHub

Title Body

The default ASP.NET web server that launches from within Visual Studio (Casini) is a little buggy on my development machine, so I like to publish to a local IIS instance on my dev machine and look at the web application there. However, I'm not automatically in "Debug Mode" when I launch the application this way. I know that VS 2010 has an "Attach to Process" debug feature, but I'm not sure exactly how to use it. What do I need to do to be able to debug a local IIS ASP.NET web application from within Visual Studio? Specifically: What settings do I need to change in the configuration of my web application? What "Package/Publish Settings" do I need to change? Is there anything I need to change in IIS? Is there anything special I need to do in the "Attach to Process" screen? Background Information: I'm running Visual Studio 2010 on Windows XP SP3 with IIS 5.1 and .NET 4.0. Additional Information: I should add that I've tried attaching to aspnet_wp.exe, but when I go to a page that I know has a breakpoint in it, I get the following message when I hover over the "open circle" breakpoint: The breakpoint will not currently be hit. No symbols have been loaded for this document.

Tags (comma-separated) Cancel