Thats a good article, and I'll be reading it in depth.
However, at a quick scan, it doesn't have anything that I can use to "log"
from within the application itself. I want to be able to log all the
details I need and then read through the log file after an application
crash.
The problem is that I can't really duplicate the problem in the lab, but
lots of customers report it, So, I want log files from real users...
Regards
Simon
--
Simon Verona
"rowe_newsgroups" <ro********@yahoo.comwrote in message
news:11**********************@e3g2000cwe.googlegro ups.com...
You may have already seen this as it's on the start page of visual
studio, but this link addresses some of these issues. Not sure if it
will solve any of your problems but it should give you some ideas on
how to proceed.
http://msdn.microsoft.com/msdnmag/is...t/default.aspx
Thanks,
Seth Rowe
Simon Verona wrote:
>I have a problem with my application crashing on-site.. (It just
disappears
with no errors!).
I suspect that I am running out of some sort of resource during the time
that the application is running.
To assist in tracing what is going on, I want to trace and log the
resources
that my application is using (such as amount of memory, threads etc). I
have a central place in my code that I can log all this information, but
I
have two questions :
1. What information should I be logging ?
2. How do I get this information (WMI?? Win32 calls?? somewhere
in
the diagnostic class?)
Thanks in advance for any ideas.
Regards
Simon
--
Simon Verona