How to make VS stop on first chance exceptions

[Academia]

I see the following in my "Output" pane when I run my program.

A first chance exception of type 'System.NullReferenceException' occurred in
....

I believe there is a way to configure VS so that it will stop on such
exceptions but can not find it.

Can you tell me how to set that?



Do you know what "first chance exception" means?



Thanks

I'm guessing some property is being set by Designer generated code that
should only be set at run time.

 

[Peter Macej]

I believe there is a way to configure VS so that it will stop on such

exceptions but can not find it.

I haven't tried but I believe this will help:
http://msdn2.microsoft.com/en-us/library/d14azbfh.aspx

Do you know what "first chance exception" means?

You can read more about it and find links to explanation in my article:
http://www.helixoft.com/blog/archives/24

 

[Academia]

I right-clicked and unselected "Exception Messages"

Now I worry that unhandled exceptions will go unnoticed.

Will the debugger still stop on unhandled exceptions?


Thanks

 

[Peter Macej]

Will the debugger still stop on unhandled exceptions?

Yes, unless you haven't disabled unhandled exceptions under
Debug-Exceptions menu. Now you have only disabled exception messages in
output window. Exception assistant will still pop-up for unhandled
exceptions.

 

[Academia]

Yes, unless you haven't disabled unhandled exceptions under
Debug-Exceptions menu.

Are you refering to the top level (or items in) "Common Language Runtime
Exceptions" in the Debug-Exceptions menu?


Thanks for all the help


ps I think you meant "have disabled" didn't you?

 

[kimiraikkonen]

I right-clicked and unselected "Exception Messages"

Now I worry that unhandled exceptions will go unnoticed.

Will the debugger still stop on unhandled exceptions?

Thanks

Set "try-catch-finally "blocks for the critical execution areas where
you suspect, thus you can catch an unhandled exception when it occurs.

 

[Academia]

Set "try-catch-finally "blocks for the critical execution areas where
you suspect, thus you can catch an unhandled exception when it occurs.

thanks