Visual studio stops debugging VSTO application, but work fine without debug.

Question

0.00/5 (No votes)

See more:

I have a VSTO add-in that works perfectly when running normally. However whenever I try to debug, PowerPoint closes and debugging stops shortly after starting up. No exception thrown, no messages.

Again, works perfectly as long as i'm not debugging. Seems to be a problem with VS or the environment because this isnt experienced on other developer machines.

Any thoughts on why the debugger is crashing on this particular machine or how to diagnose?

What I have tried:

I have tried other machines and it works fine.

Posted 28-Aug-19 14:35pm

BMauk

Add a Solution

Comments

Richard MacCutchan 29-Aug-19 6:38am

Try to find what is different between the machine where it fails and the ones where it succeeds. It may be a Visual Studio problem or a Windows problem, but without much more information it is impossible to guess.

BMauk 29-Aug-19 10:30am

What i'm struggling with is how to get more information as to what is causing the debugger to stop. Does VS log this stuff anywhere?

Richard MacCutchan 29-Aug-19 11:04am

The only way to find out is look at the VSTO documentation, or the documentation that is specific to the add-in you are using. Also look at the debug output Windows to see if it is displaying any messages.

BMauk 29-Aug-19 11:47am

Not sure what you mean. I am building this add-in myself.

Richard MacCutchan 29-Aug-19 12:38pm

Then you are the best person to understand why it is not working.

BMauk 29-Aug-19 12:59pm

Again, the Add-in works just fine. I just cannot debug it on this specific machine, but debugging works on others. This leads to a conclusion that it is not the code, but something with the specific environment on this machine.

Richard MacCutchan 29-Aug-19 14:43pm

That is what I suggested this morning.

[no name] 29-Aug-19 9:12am

Maybe you have a break point, assert, compiler directive, etc that only runs when debugging. It happens.

BMauk 29-Aug-19 10:29am

None. Thanks for the thought though. Again, works completely fine on other machines...

Tried a clean install of Visual Studio no the machine as well to no success.

CHill60 29-Aug-19 10:31am

Have you tried cleaning the solution and rebuilding on the machine causing the problems?

BMauk 29-Aug-19 11:46am

Yes.

BMauk 29-Aug-19 13:00pm

I have new info...
I seem to have isolated the specific issue on this machine, but i cannot explain it.

The add-in has a WPF control in a custom action pane, hosted by a ElementHost on the windows form.

If I comment out all the WPF so that WindowsFormsIntegration, PresentationCore, etc are removed from the solution, then I can debug on this machine. Note: I don't need to do this on other machines.

Any thoughts?

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)