I am trying to debug an old ASP.NET program that was handed to me. But I find that I cannot step into server side code (web services) running in IIS.
I am using Visual Studio 2008 in Windows 10 with .NET 2.x. Both Visual Studio and IIS are running from the same desktop computer (my PC).
Previously in an older version of the ASP.NET program that ran in Windows-XP using Visual Studio 2003, I could step into the server side code by attaching to the process "aspnet_wp.exe". In this newer IIS, aspnet_wp.exe is no more. I am not sure what has replaced it. I assume it is "w3wp.exe". Unfortunately, I still cannot step into server side code when I attach to w3wp.exe. I have also tried attached to "aspnet_state.exe"; but no difference. Which process that I am supposed to attach to?
One strange thing is that Visual Studio used to prompt me to attach to a process (forgot which process) when I was stepping through the program last week. I don't remember if I was able to step into server side code or not at that time. But now Visual Studio has stopped prompting me. How do I ask Visual Studio to resume prompting me to attach to a process?
Yes, the "debug" option in Web.config in both the client side and server side programs are "true", like this:
<compilation defaultLanguage="c#" debug="true" />
Please let me know if there is anything else that I can try. Thanks.