c＃，当在其他系统上运行编译的应用程序...，ScintillaNET签名错误？ [英] c#, when running compiled app on other systems..., ScintillaNET signature Error?

问题描述

当我分发我开发的软件时，我遇到问题，编译的.exe在我的系统上运行正常，但解析到其他人时，它会在32位和64位系统上显示以下错误。

我已经尝试了许多编译选项，包括混淆，构建任何CPU，构建64位和32位，我也尝试过，在其他系统上构建，所有.dll都是在包中提供的，我甚至累了合并.dll，我可以没有打破许可协议等。

甚至在其他系统上注册了所有.dll。

任何想法？
我做了一些谷歌搜索，但作为最后的手段，我不得不问这里，知道我的运气这将是一个明显的事情，错误让我相信，dll不在那里，但他们是...

以下是以下错误：

 问题签名：
 
问题事件名称：CLR20r3 
问题签名01：testtool.exe 
问题签名02：1.0.0.0 
问题签名03：4e1ec8bf问题
签名04：ScintillaNet 
问题签名05：2.2.3581.19319 
问题签名06：4adf566e 
问题签名07：66e问题
签名08：5c 
问题签名09：System.IO.FileNotFoundException 
操作系统版本：6.1.7600.2.0.0.272.7 
区域设置ID：1033 
附加信息1：0a9e 
附加信息2：0a9e372d3b4ad19135b953a78882e789 
附加信息3：0a9e 
附加信息4：0a9e372d3b4ad19135b953a78882e789 
  

...在我编译的系统上运行正常

以上引导我认为dll不在那里，但他们是。

谢谢你，
Scott

解决方案

如果你有一个.NET应用程序崩溃，没有明显的理由在另一个系统，并且错误报告提示事件抛出异常（如 System.IO.FileNotFoundException ），您应该添加一个未处理异常的处理程序（ AppDomain.CurrentDomain.UnhandledException ），然后使用一个消息框输出整个异常（ e.ExceptionObject.ToString（））。堆栈跟踪应该更多地了解发生了什么（您还可以使用其他异常属性）。使用PDB文件的调试版本还将提供行号。

请参阅 http://www.csharp-examples.net/catching-unhandled-exceptions/

重要的是添加这个事件处理程序启动您的应用程序，在异常有机会发生之前。使用像Windbg这样的工具对于托管的异常通常是过度的。

I am having problems when I distribute software I developed, the compiled .exe runs fine on my system but when parsed to others it displays the below error, on both 32 bit and 64 bit systems.

I have tried many compile options, including obfuscating, building for any CPU, building for 64bit and 32, I also tried, building on other systems, all .dlls are supplied in the package, i even tired merging the .dlls that I could without breaking license agreements etc.

Even registered all .dlls on the other system.

Any ideas? I did some googling, but as a last resort i have had to ask here, Knowing my luck it will be something obvious, The error leads me to believe the dlls are not there but they are...

Here is the error below:

Problem signature:

Problem Event Name: CLR20r3 
Problem Signature 01: testtool.exe
Problem Signature 02: 1.0.0.0 
Problem Signature 03: 4e1ec8bf Problem
Signature 04: ScintillaNet 
Problem Signature 05: 2.2.3581.19319
Problem Signature 06: 4adf566e 
Problem Signature 07: 66e Problem
Signature 08: 5c 
Problem Signature 09: System.IO.FileNotFoundException
OS Version: 6.1.7600.2.0.0.272.7
Locale ID: 1033 
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

...Runs fine on the system I compile it on.

The above leads me to think the dll's are not there... but they are.

Thanks kindly, Scott

解决方案

If you have a .NET app that crashes for no apparent reason on another system, and the error report hints at the fact that an exception is thrown (like System.IO.FileNotFoundException), you should add a handler for unhandled exceptions (AppDomain.CurrentDomain.UnhandledException) and then just output the whole exception (e.ExceptionObject.ToString()) with a message box. The stack trace should give some more insight into what is happening (you can also make use of the other Exception properties). A debug build with PDB files will additionally provide line numbers.

See http://www.csharp-examples.net/catching-unhandled-exceptions/

It's important to add this event handler at startup of your app, before the exception has a chance to happen. Using tools like Windbg is usually overkill for managed exceptions.

这篇关于c＃，当在其他系统上运行编译的应用程序...，ScintillaNET签名错误？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！