Skylar,
In general Windows catches and logs application problems and if say an
external problem did cause your app to crash, perhaps it has been logged in
one of the system defined event logs?
I would do a quick reinstall of the .NET Framework, that should take care of
a problematic .NET Framework.

Signature
Carsten Thomsen
Enterprise Development with VS .NET, UML, and MSF
http://www.apress.com/book/bookDisplay.html?bID=105
>I haven't check that, is there generic event logs that I could check? My
>program isn't created to write to anything specific. Also, the computer
[quoted text clipped - 6 lines]
>> anything logged to the event logs at the time the exception is thrown? Is
>> any other .NET application running fine on the machine?
Skylar Challand - 01 Nov 2004 22:55 GMT
We did a complete uninstall of the .NET Framework, did all the Windows
Updates and SP2 install as well. Reinstalled the app and still got the
same error. I'm baffled at this problem.
Can you point me in the direction where I might find these event logs
specifically? I havent been able to find any information on them from
google.
Also, I'm going to try running another .NET application to see if I get
this error. Is there any .NET self checking software apps out there or
do you think it would be best if I just make a quick simple "Hello,
world!" app.
Thanks again
> Skylar,
>
[quoted text clipped - 4 lines]
> I would do a quick reinstall of the .NET Framework, that should take care of
> a problematic .NET Framework.
CT - 02 Nov 2004 07:52 GMT
A simple Hello World should do to see if the .NET Framework is working as
it should. With regards to the event logs, have you looked at the Event
Viewer utility in the Administrative Tools menu?

Signature
Carsten Thomsen
Enterprise Development with VS .NET, UML, and MSF
http://www.apress.com/book/bookDisplay.html?bID=105
> We did a complete uninstall of the .NET Framework, did all the Windows
> Updates and SP2 install as well. Reinstalled the app and still got the
[quoted text clipped - 19 lines]
>> I would do a quick reinstall of the .NET Framework, that should take care
>> of a problematic .NET Framework.