I never said it would work. It is unsupported. Alot of what you see in the
CF is limited to the CF BCL. Even as far as the Message property sometimes
does not get populated so you might for instance just get a type of
exception thrown and no more information.
This goes back to what I said before. You shouldn't really need to know
stack traces and line numbers in a production app. This should only be for
debugging reasons - while it can be painful not to have lines numbers during
debugging. Write unit tests and try to get a 100% code coverage so that you
know if exceptions are thrown you can recover from them or they are
expected.
You could add diganostics using standard .NET tracing to tell you more info.
This is good practice anyway.
--
Simon Hart
Visual Developer - Device Application Development MVP
http://www.simonrhart.com
A .NET Compact Framework application does not contain line numbers when an
exception is thrown because Visual Studio does not deploy the PDB (Process
Debug File) file to the device.
Even if PDB file is deployed It doesn't solve the problem.
Anyway, added Error Reporting module, but somehow it is limited to
unmanaged code exception handling.
When exception happens in my CF app, all I see is standard window with
quit and details buttons and no kdmp file created.
Is there a way to tune this behaviour?