Mark Gabarra
MS CLR team
This posting is provided "AS IS" with no warranties, and confers no rights.
I just wasted half a day trying to troubleshoot a missing DLL. The
Framework SDK's steadfast refusal to install on XP Tablet didn't help the
situation.
Outputting to stderr doesn't do much for WinForms apps - you normally never
see it, even if you launch from a command line. Here's a hint for the next
person to run into this error. Run your application from the command line,
redirecting stderr to a file:
myapp.exe 2> error.log
When the application dies, the exception information and stack dump will be
written to the file. (I wish I had figured this out 4 hours ago).
-Frank
"Mark Gabarra [MSFT]" <ma...@online.microsoft.com> wrote in message
news:BNLVJseN...@cpmsftngxa06.phx.gbl...
Application popup: apllication.exe - Common Language Runtime Debugging
Services : Application has generated an exception that could not be
handled.
Process id=0x41c (1052), Thread id=0x770 (1904).
Click OK to terminate the application.
Click CANCEL to debug the application.
Also i have tried the followin command from command line.
Application.exe > Error.log
After run the exe , Error.log has created with 0 bytes.
Can you please help me to solve this issue?
Thanks,
Mohan
mo...@tek.com
I would re-install the framework on the machine exhibiting the error.
--
Patrick Steele
Microsoft .NET MVP
http://weblogs.asp.net/psteele