How best to avoid unhandled exceptions in MS code from hanging my

[GrahamS]

Hi,

As described in various other posts - I am having a few issues where I get a
popup dialog box from within the OS - or managed wrappers etc. These are
being caused by apparently unhandled exceptions possibly in threads outside
of my app (Serial port and Socket programming).

They manifest as a popup dialog stating that my app must be closed down.

Well - on an embedded product with NO USER - this is pretty catastrophic :-O.

SO - as CE does not support 'services' - how 'should' I build my code so
that these will not occur and will instead cause the app to shut down either
gracefully with an exception or at least just to exit the app - as my outer
layer code will restart it again ;-O.

Do I need to build as a command-line app ?? - as there is no UI - it 'ought'
to shut down without asking for user intervention ??.

I would normally build this type of app on a PC as a 'windows service' - but
.......

Many Thanks

Regards

Graham

 

[Chris Tacke, eMVP]

If it's an OS dialog, you need to modify the CE image to not show them or
remove GWES altogether.


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com

 

[Chris Tacke, eMVP]

If it's an OS dialog, you need to modify the CE image to not show them or
remove GWES altogether.


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com