I put tracing in all of my apps with an option to turn it on and off. This
allows the client to turn it on and go about their business until they hit
an error, but not build up unnecessary logs or performance hits when it's
off. They can then send you the trace log so you can reproduce the steps.
You can also add a "global error handler" so that any exception that bubbles
to the top can be handled gracefully and recorded (logged, give instructions
to user on what to do, or at worst msgboxed).
Example here:
http://samples.gotdotnet.com/quickst...orHandler.aspx
Note if you obfusicate the strack trace isn't going to be worth much.
--
Justin Weinberg
Designing a PrintDocument? Drawing to forms?
Check out GDI+ Architect at
www.mrgsoft.com
"John" <jo**@nospam.in fovis.co.uk> wrote in message
news:Oe******** ******@tk2msftn gp13.phx.gbl...
Hi
I am having difficulty figuring out the source of errors in an app that is
delivered to a client. Is there a way that a compiled app can give the
location of the error, such as procedure, line no (if possible) etc.?
Thanks
Regards