M
Matt MacDonald
Hi all again,
I've been fighting with the Visual Studio.Net CLR debugger for a while and
am getting pretty fed up. I'm trying to debug an asp.net application. I
have all my debug tags set to true. And I have debugging enabled on my web
server. When i try to do standard debugging, I get an error saying that
debugging cannot start because there is no managed code running in the
process, and that I need to have the code running and then attach. Fine, so
I start the app in a browser window and then try to manually attach to the
process. Same thing. The only way I can get it to run and debug is by
enabling "Unmanaged Code Debugging" which is extremely slow and crashes
everyother time. Anyone have any experience with this problem? I already
re-installed the .net SDK so I'm pretty sure that's not the problem.
Thanks,
Matt
I've been fighting with the Visual Studio.Net CLR debugger for a while and
am getting pretty fed up. I'm trying to debug an asp.net application. I
have all my debug tags set to true. And I have debugging enabled on my web
server. When i try to do standard debugging, I get an error saying that
debugging cannot start because there is no managed code running in the
process, and that I need to have the code running and then attach. Fine, so
I start the app in a browser window and then try to manually attach to the
process. Same thing. The only way I can get it to run and debug is by
enabling "Unmanaged Code Debugging" which is extremely slow and crashes
everyother time. Anyone have any experience with this problem? I already
re-installed the .net SDK so I'm pretty sure that's not the problem.
Thanks,
Matt