Why won't a C # application run on another computer?

Question

I have been developing the application for about 2 months. This is the first time I have done any of this size before. Now, when I get closer to the fact that all processes function the way I want them, I get the error below when I try to start the application.

I created applications before it was just fine ... actually better on other machines. But this app destroys my chops.

Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: logopicking.exe Problem Signature 02: 1.0.0.0 Problem Signature 03: 4f4e6509 Problem Signature 04: System.Drawing Problem Signature 05: 4.0.0.0 Problem Signature 06: 4ba1e086 Problem Signature 07: 30 Problem Signature 08: 14 Problem Signature 09: System.IO.FileNotFoundException OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789 

So that it gives me an error.

To add additional information, I will send messages

 using System; using System.ComponentModel; using System.Drawing; using System.IO; using System.Windows.Forms; using Interop.QBFC11; 

I do not know if there was something wrong with any of them, a problem may arise that would prevent the application from starting.

Answer 1

Reporting a System.IO.FileNotFoundException error, you are missing a component or trying to read a file that does not exist.

Make sure that you have installed the correct version of the .Net infrastructure on this second PC (depending on which version of Visual Studio you are using), and you will probably need to install everything that is required by Quickbooks, as well as on the second machine.

Answer 2

you get a System.IO.FileNotFoundException . Your application is trying to access a file that it cannot find on the "other machine"

this link will help you: http://channel9.msdn.com/Forums/TechOff/258689-NET-20-Win-App-Eror-EventType-clr20r3

from there:

"Deploy an UnhandledExceptionHandler and log the exception information in the event log so you can get more detailed information about what causes your application to crash and in what context."

 // C# 2.0 static void Main(string[] args) { AppDomain.CurrentDomain.UnhandledException += new UnhandledExceptionEventHandler( delegate(object sender, UnhandledExceptionEventArgs e) { if (e.IsTerminating) { object o = e.ExceptionObject; Debug.WriteLine(o.ToString()); } } ); // rest of your Main code }