Exception Assistant, what is your malfunction.

Sara Ford writes on how to disable to exception assistant, but what I really want to know is how to conditionally disable the assistant. I haven’t looked too hard to uncover this because it only seems to crop up under certain conditions. I think the problem is when you are handling the exception, but you are not handling it in a portion of the stack that is being debugged by studio. So what happens is you end up being notified about the exception even though it will subsequently be handled. This may be the desired result sometimes, but other times, it most certainly is not.

A good example of this is if you are using nunit’s ExpectedException attribute. Even though this causes the nunit framework to handle the exception and turn it into an assertion failure, you still get the assistant popping up at the time the exception is raised, trying to be helpful. It would be nice if there was an attribute we could use to disable the assistant for a call, but hey, maybe there already is! Or alternatively, it would be useful if it’s possible to disable the assitant at a project level.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: