• Advertisement
Sign in to follow this  

[.net] Wicked problem occurred in debugger startup session

This topic is 4199 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I wrote a .NET application with MDX using VS2005. Sometimes when I press F5 to launch the debugger, there's a good chance that debugger will get stuck in startup session loading DLLs. Application is not up. Form is not shown. No response at all. Soon VS2005 will get in busy state too. I thought it was my fault that some resources are not properly disposed when I start debugger last time, but it seems not what I thought. I can't do anything but to restart debugger (once or a couple of times) to get it run normally. Has anyone come across this same situation? Any suggestion for this problem? Many thanks.

Share this post


Link to post
Share on other sites
Advertisement
Just a guess,

But go into Debug->Exceptions->Managed Debugging Assistants, and untick LoaderLock.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement