Reputation: 372
I am having difficulty attaching the Visual Studio debugger to the IIS w3wp process. In certain repeatable circumstances, I am finding that symbols do not appear to be loaded based on how the w3wp process is launched.
For example:
Recycling the app pool and loading any aspx page first from any .NET project results in the debugger working just fine, and my breakpoints are hit.
Recycling the app pool and loading any ASP Classic page first, results in symbols not being loaded, even if I subsequently load to an aspx page before attaching to the process.
I think it might be something to do with the way Visual Studio automatically determines which code types to debug, but I don't know enough about this to be sure.
Any help would be greatly appreciated.
Upvotes: 2
Views: 1958
Reputation: 149
When you debug - do you deploy the same application version to your IIS?
I believe that by default in VS settings (Tools -> Options -> Debugging) an option "Require source files to exactly match the original version" is enabled, try to disable it.
Upvotes: 1