.net C # Winforms.exe not starting on any other machine

Question

Ive developed a winforms application on my local machine using .net 4.0 and it works fine. I have all versions of dotnet installed.

When I copied the .exe file and all its links (full bin \ debug and bin \ release) to another computer, it just does not start. On one of my VMS, he starts visual studio express and asks if I want to connect debgger. On other machines, he does nothing.

But I can understand what is happening on earth.

I refer to the soem xceed dll that are installed in the GAC, but not on the target GAC computers, can be a problem?

How do I tell you what the hell is going on?

Pete

Answer 1

Yes, the target computer must have xceed dlls (and all other reference dlls) that are included in the application directory or GAC.

You can try to point “Copy local = true” to suspicious links and rebuild your project so that these DLLs are specifically included in compiled assemblies.

Answer 2

Have you verified that the .Net Framework version is installed on another machine? Otherwise, try to publish the application using the ClickOnce tool.

ClickOnce will download and install any missing dependencies for the .NET Framework, if necessary.

Answer 3

If you decompose pdb files into one virtual machine with VS Express installed, you can connect the debugger and view the exception information. And yes, a missing assembly can (or better: will) cause this behavior if the assembly is not only referenced, but actually used in your application. I usually recommend that you implement some kind of error logging (either in the event logs or in a text file).