Home/ Questions/Q 6170999
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T23:08:13+00:00

I am having problems when I distribute software I developed, the compiled .exe runs

  • 0

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

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    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.

    • 0