c#，在其他系统上运行编译的应用程序时...，ScintillaNET 签名错误？
当我分发我开发的软件时遇到问题，编译后的 .exe 在我的系统上运行良好，但在解析给其他人时，它在 32 位和 64 位系统上显示以下错误。
我尝试了很多编译选项，包括混淆、为任何 CPU 构建、为 64 位和 32 构建，我也尝试过在其他系统上构建，所有 .dll 都在包中提供，我什至厌倦了合并我不需要的 .dll违反许可协议等。
甚至在其他系统上注册所有.dll。
有什么想法吗？ 我做了一些谷歌搜索，但作为最后的手段，我不得不在这里问，知道我的运气这将是显而易见的事情，这个错误让我相信 dll 不在那里，但它们确实存在......
这是下面的错误：
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
。 ..在我编译它的系统上运行良好。
上面的内容让我认为 dll 不存在......但它们确实存在。
亲切地感谢， 斯科特
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
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果您有一个 .NET 应用程序在另一个系统上无明显原因崩溃，并且错误报告暗示抛出了异常（如 System.IO.FileNotFoundException），则您应该添加未处理的异常 (
AppDomain.CurrentDomain.UnhandledException) 的处理程序，然后使用消息框输出整个异常 (e.ExceptionObject.ToString())。堆栈跟踪应该可以更深入地了解正在发生的情况（您还可以使用其他异常属性）。使用 PDB 文件的调试版本将另外提供行号。请参阅http://www.csharp-examples.net/捕捉-unhandled-exceptions/< /a>
在应用程序启动时、在异常有机会发生之前添加此事件处理程序非常重要。使用像 Windbg 这样的工具对于托管异常来说通常是大材小用。
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.