Last post Apr 26, 2009 08:36 PM by audux
Apr 15, 2009 09:43 PM|audux|LINK
I was unable to perform debugging using vs2003, I already set debugging asp.net to true in properties section, but still this won't work.
I tried reinstalling vs yesterday it debugging works after. But this morning the issue was back without any changes made before i shutdown my computer yesterday.
I notice that after i press F5 to start my web app, debugging options such as pause or stop does not appear after the project was loaded to the explorer. This allows me to press F5 again when I switch back to the source code.
Can anyone help me with my issue to vs2003, I already spend a lot of time finding anwers to my vs2003.
Thanks everyone for any help.
Apr 16, 2009 12:14 AM|whighfield|LINK
Have you gone through this guide
Apr 16, 2009 08:19 PM|audux|LINK
I've tried config to IIS, VS properties and Web.config and found out that my problem is that the process aspnet_wp.exe is not automatically attached upon debugging the project.
This were fixed everytime I reinstall my VS but for some time it goes back to the problem again, Is there a way so automatically attach the process again and after that how could i avoid dettachment of the process?
Apr 19, 2009 11:57 PM|Thomas Sun – MSFT|LINK
If we disable Add-ns (“Tools” | “Add-in Manager”) and run “devenv.exe /safemode” loading only the default environment and services, do we still have the problem? This can eliminate the possibility that third party Add-ins are causing problems.
Besides, we can “devenv.exe /resetskippkgs" to avoid loading problem VSPackages.
We also can attach to running process from Visual Studio debugger. For more information, see
I look forward to receiving your test results.
Apr 26, 2009 08:36 PM|audux|LINK
Thanks for the info, I believe manual attach of the process resolves my issue.
This should be better now.