There is a power toy that may help you sort out the root of the problem, the
..NET CF Logging Configuration that you can install from here:
http://www.microsoft.com/downloads/d...displaylang=en
--
Alberto Silva
http://www.moving2u.pt - R&D Manager
http://msmvps.com/AlbertoSilva - Blog
Microsoft MVP - Device Application Development
"pezi" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> hello
> i'm developing an application for a wm6-device. sometimes the application
> suddenly is closed without throwing any exception or anything else.
>
> ----------------
> try
> {
> AppDomain.CurrentDomain.UnhandledException +=
> new
> UnhandledExceptionEventHandler(CurrentDomain_UnhandledException);
> ...
> Application.Run(...);
>
> }
> catch (Exception e)
> {
> MessageBox.Show(...);
> }
> catch
> {
> MessageBox.Show(...);
> }
> ----------------
>
> as you can see in the code-block above i already catch all exceptions
> (even the unhandled ones) but apparently there are some more
>
> does anyone know what could be happening here respectively how to catch
> this exception (or whatever it is)
>
> tia
> pezi
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 4341 (20090817) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
__________ Information from ESET NOD32 Antivirus, version of virus signature database 4341 (20090817) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com