Why VS2010 debugger is stopped when extern dll is loaded?

Question

0.00/5 (No votes)

See more:

VS2010

I converted 2 of my VS2008 solutions to VS2010 .NET 4 Client Framework. One solution is full managed (C#) and another is mixed.

Now my debugger works fine until object from extern dll or object from cpp project is referenced. Then application freezes.

If I choose Enable unmanaged code debugging then breakpoint is hit from extern dll (why?) and I can choose continue. But I cannot change code because unmanaged code debugging doesn't allow that.
With that option referencing cpp object still causes application to freeze.

If I start without debbuging (CTRL+F5) everything works fine! But i want to use debugger so I can change code while debugging.

Posted 5-Mar-12 3:53am

nihil007

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Not Active · Answer 1 · 2012-03-05T04:37:00

Solution 2

You can't change the code because you are in two separate environments, managed and unmanaged. Your main application thread, the one you are debugging, is a managed application and only has the references and debug symbols for the unmanaged code, it doesn't have the editor files.

Of course CTRL+F5 works because you are of course not using the debugger.

Posted 5-Mar-12 4:37am

Not Active

Comments

nihil007 6-Mar-12 4:26am

Ok, I understand that.

But the same worked in VS2008. Application did not freeze in VS2008 when it comes on external dll. Just it stepped over and debugger worked on my code only. Now it freezes on extern dll.