I support the .NET 2.0 Winforms application, which is pretty widely used. In rare cases, we receive a support request from a client in which the application returns a .NET AS SOON runtime exception when trying to start the application.
In the past, we helped the client reinstall the .net structure, and very often it works ... but sometimes not.
In such a situation, you could use Windows Debugging Tools to determine the cause of the problem. If you wanted to download debugging symbols to the target computer (you need to avoid it, as this may be several hundred MB of material to be downloaded to the target.)
Is this redundant for a .net application? Any alternatives. How are you going to debug this. It would be useful to evaluate the non-specific step by step. Of course, this application is compiled as a RELEASE configuration on the target machine. The client will most likely not have installed developer tools or debugging tools. Usually we have access to a computer with remote control. Repeat. This happens SO the client tries to start the application, and it will immediately work.
What is the fastest way to solve this problem for the client?
The following is an example of a recent error from the event log.
EventType clr20r3..exe P2 2010.1.0.0, p3 4B857AFD P4 BLAH BLAH system.invalidoperation, P10 NIL.
Source: .NET Runtime 2.0 Error. EventID: 5000
Thanks in advance.
Set