CODEWITHSUNDEEP
.netvisual-studiodebuggingexception
Steven
Steven

Reputation: 172616

Where did my Visual Studio exception assistant go?

Since a couple of weeks the Visual Studio (2008 9.0.30729.1 SP) Exception Assistant has stopt appearing while debugging using the C# IDE. Instead the old ugly and useless debug dialog comes up:

DebugExceptionModal
(source: msdn.com)

To make sure, I've checked the following:

How can I get the Exception Assistant back? Who gives me the golden tip?

Upvotes: 16

Views: 6059

Answers (6)

itsho
itsho

Reputation: 4800

I've tried every solution suggested on this page, in vain. In my case, I tried uninstall and reinstall (yes, it was that annoying). And it still didn't solve the issue.

The only thing actually solved it, was unchecking "Enable unmanaged code debugging" from project properties => Debug:

unchecking "Enable unmanaged code debugging" from project properties -> Debug in VS2010

:-)

Upvotes: 9

husterk
husterk

Reputation: 184

I had the same problem till I reset my Visual Studio settings (default to C#) then configured the debugger with the following settings:

  • Tools -> Debugging -> General -> Enable the exception assistant (CHECKED)

  • Tools -> Debugging -> General -> Unwind the call stack on unhandled exceptions (NOT CHECKED)

  • Tools -> Debugging -> General -> Enable Just My Code (CHECKED)

  • List item Tools -> Debugging -> General -> Show all members for non-user... (NOT CHECKED)
  • Tools -> Debugging -> General -> Warn if no user code... (CHECKED)

It looks as though an attempt to unwind the call stack on an unhandled exception is causing the debugger to crash in VS2013.

Upvotes: 3

pvasek
pvasek

Reputation: 1156

You can also see this dialog if you have enabled Debuggers > Native Code in your project setting. If you turn it off it should work again.

Upvotes: 15

Dimos
Dimos

Reputation: 41

Had exactly the same problem, so i found this post here. I did two things, don't really know what actually solved this...

First was applying the VS SP1

Second was going to Tools -> Import and Export Settings -> Reset all settings

and then selecting c# as the language setting. The previous user had c++, so there might be a connection.

SOLVED

Upvotes: 4

Hans Passant
Hans Passant

Reputation: 941277

"Debug / Exceptions / Common Language Runtime Exceptions / Thrown" is on.

That's your problem, makes the debugger stop on the first chance exception. Very useful, but not if you prefer the exception assistant. Turn it off.

Well documented question btw, my compliments.

Upvotes: 1

please delete me
please delete me

Reputation:

It's a real shot in the dark but it might be worth trying uninstalling some recent Windows updates. The recentish KB978037 update broke debugging of console mode programs, so this has made me (for one) a bit suspicious of them now:

http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/e6d4a4f5-7002-401a-90e1-6174d7f9e3ca

To be fair, this is the first time I've noticed anything really awful arising from a patch, but it's worth a shot. (If you turn off the automatic install of updates, then you can try this stuff out without too much fear. Windows Update seems to re-download any patches you uninstall so you can easily put them back again.)

Upvotes: 2

Related Questions