Windows Server 2003上的mscorwks.dll导致.net Runtime 2.0错误 [英] .net Runtime 2.0 error due to mscorwks.dll on Windows Server 2003

问题描述

我正在尝试测试c#应用程序，因此我将其尽可能地保持运行.问题是，它随机地在Windows Server 2003上崩溃，没有任何异常.在Windows 7上运行时，它可以完美地工作.直到现在都没有崩溃.在Windows XP上，它也不会崩溃.反馈的唯一方法是查看事件查看器，并且出现以下错误:

I''m trying to test a c# application so I''m leaving it running as far as it can. The problem is that, radomly, it crashes without any exception on windows server 2003. When running it on windows 7, it works perfectly. No crash till now. On windows xp, it does not crash too. The only way to get a feed back is to look at the event viewer and I get the following error:

Event Type: Error
Event Source:   .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID:   1000
Date:       <date>
Time:       <date>
User:       N/A
Computer:   <machine name="">
Description:
Faulting application <application name="">, <application version="">, stamp 4ce54d0f, faulting module mscorwks.dll, version 2.0.50727.1433, stamp 471ef729, debug? 0, fault address 0x000f675b.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.</application></application></machine></date></date>

有没有人遇到问题?

预先感谢.

Is there anyone that encountered the problem?

Thanks in advance.

推荐答案

获取反馈的唯一方法是查看事件查看器"

这是不正确的.您已经编写了代码，并且完全可以控制.没有什么可以阻止您添加检测和/或日志记录来监视代码中的条件.像专业人员一样开发软件.

像专业软件一样，应用程序应处理异常，包括UnhandledException，并且不要完全崩溃.

"The only way to get a feed back is to look at the event viewer"

This is incorrect. You wrote the code and are in complete control. There is nothing stopping you from adding instrumentation and/or logging to monitor conditions in your code. Like professionals develop software.

Also like professional software an application should handle exceptions, including UnhandledException, and not crash outright.

这篇关于Windows Server 2003上的mscorwks.dll导致.net Runtime 2.0错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！