ASP.NET Debugging

[Brian Henry]

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.

[Natty Gur]

Interesting,

Is this happened while you trying to debug simple page or complex page
that calls other classes? I've seen this error for .Net assemblies
registered in COM+ as server application. Did you change application
isolation level from IIS MMC?

Natty Gur[MVP]

blog : http://weblogs.asp.net/ngur
Mobile: [phone]
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!

[Steven Cheng[MSFT]]

Hi Brian,

From your description, when you are using Visual Studio .NET 2003 and you
try to debug an ASP.NET Web application , you may receive the following
error message:

Unable to attach to the process. There is no managed code running in
the process. In order to attach to a process with the .NET debugger,
managed code must be running in the process before attaching.

and even not able to manually attach the workerprocess to debug, yes?

Based on my experience , such problem is mainly due to the .net framework
install corrupt, there're some former issues with the similar symptom and
were resolved by repair or reinstall the .net framework. I recommend that
you have a try on repairing the framework, if still no success, I recommend
that you reinstall the framework and restart the machine after that.

#HOW TO: Troubleshoot Microsoft .NET Framework 1.1 Installation Issues
http://support.microsoft.com/?id=824643

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx

[Steven Cheng[MSFT]]

Hi Brian,

Have you had a chance to check out the suggestions in my last reply or have
you got any further ideas on this issue? If there're anything else we can
help, please feel free to post here. Thanks.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx

[Brian Henry]

Thanks

"Steven Cheng[MSFT]" <v-******@online.microsoft.com> wrote in message
news:FN****************@cpmsftngxa10.phx.gbl...

Hi Brian,

Have you had a chance to check out the suggestions in my last reply or have you got any further ideas on this issue? If there're anything else we can
help, please feel free to post here. Thanks.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx