Using AppDomain.UnhandledException w/ Created Domain

[Becks25Not]

Hi All,

I have been working on a "no touch deployment" project. I have a launcher that creates a domain for the exe to run in. I noticed that my generic error handler stopped working after this was all set up. I found out that the AppDomain.UnhandledException only works in the default domain and that it was supposedly going to be corrected with 2005. Is there a workaround for adding a generic handler in created domains? or other suggestions?

Any help / ideas would be greatly appreciented!!

Thanks ~ Becca

 

[dalchri]

I use System.Windows.Forms.Application.ThreadException for my generic exception handler:

http://msdn.microsoft.com/library/d...formsapplicationclassthreadexceptiontopic.asp

 

[Becks25Not]

Hi dalchri,

Thanks for the reply ... I tried it but still no luck!!

~ Becca

 

[chiph]

The two unhandled exception handlers serve different purposes.

Becks25Not - Like you've discovered, it only works for the default domain, and you'll have to wait for the 2.0 framework to fix this.

Chip H.


____________________________________________________________________
If you want to get the best response to a question, please read FAQ222-2244 first

 

[Becks25Not]

Thanks ChipH ... that's what I was afraid of! I restructured the launcher to have a little form that says "Connecting ..." and then I just hide it so I am no longer creating the second domain.