Debugging release

  • Thread starter Thread starter bob
  • Start date Start date
B

bob

Hello,

Once I've distributed my application how do I diagnose my customers
errors (not that they'll be any). It doesn't seem to output any kind
of error log file, is there one?

Any clues?


Thanks,

Bob
 
It doesn't output a log file of its own accord, you have to programtically cause it to. It doesn't know what information you want in the log file
 
There's no automatic errorlog generated. You need to incorporate that kind
of stuff in your code.

http://logging.apache.org/log4net/

is a good example of how to do it. But it's open source, so you can't use it
in a commercial product.

What you need to do is figure out what sort of logging system you want. Do
you want to log to a text file, XML, the event log, etc?? Then write a
framework for logging the errors as they occur. But since you've already
delivered your product to your customers, you'll need to add the logging and
then ship the new version.

Unfortunately, a lot of people don't consider the need for this until after
they've shipped, at which point, it's a bit too late.

Pete
 
Hi Pete,
thanks for your info. I think my plan is to put a 'try catch' around
the application start up and in the catch pop up a 'Send error
details...' window, like explorer etc. I can then send me a copy of
the stack trace.
But if I've obfuscated my code I won't be able to understand the stack
trace. Is there anything I can do about that?

Thanks,

Bob
 
Back
Top