It's impossible to debug code in MyApplication_UnhandledException

Great, they added a new feature I understand <GGGG>, the application events.
And you have a new super event that lets you decide what to do with
unhandled application errors.
But its impossible to single step through the code you write in it if you
throw and unhandled exception in your code in the IDE to test what you
wrote.
Great thinking guys!
Anybody found a way around this spark of genius?

Any insight would be appreciated.
Bob

Robert Dufour wrote:
> Great, they added a new feature I understand <GGGG>, the application events.
> And you have a new super event that lets you decide what to do with
> unhandled application errors.
> But its impossible to single step through the code you write in it if you
> throw and unhandled exception in your code in the IDE to test what you
> wrote.
> Great thinking guys!
> Anybody found a way around this spark of genius?

Run your app outside of the IDE. Then attach the IDE to the running
app. It will then hit your breakpoint in the exception handler.

Chris exactly how do you attach the IDE to the running app? Learning
something new here.
Thanks for your help.
Bob
"Chris Dunaway" <dunawayc@gmail.com> wrote in message
news:1163683345.479451.175750@m73g2000cwd.googlegroups.com...
> Robert Dufour wrote:
>> Great, they added a new feature I understand <GGGG>, the application
>> events.
>> And you have a new super event that lets you decide what to do with
>> unhandled application errors.
>> But its impossible to single step through the code you write in it if you
>> throw and unhandled exception in your code in the IDE to test what you
>> wrote.
>> Great thinking guys!
>> Anybody found a way around this spark of genius?
>
> Run your app outside of the IDE. Then attach the IDE to the running
> app. It will then hit your breakpoint in the exception handler.
>

Robert Dufour wrote:
> Chris exactly how do you attach the IDE to the running app? Learning
> something new here.

Tools -> Attach To Process

Or

Ctrl-Alt-P