Quote Originally Posted by Evil_Giraffe View Post
I believe ILMerge is no longer updated by Microsoft. If this is the case (and I'm not 100% sure that it is) then it is possible that .NET 4 assemblies get mangled by ILMerge?
Hmm, yes that actually is true. My problem was that my application is not compatible with ILMerge since it is using the .NET Framework 4. However, I read up about .NET 4 issues on the official Microsoft Research website, and ILMerge is actually compatible with .NET 4; all I had to do to get this compatibility was add another option to the ilmerge command in the Command Prompt:

Code:
/targetplatform:v4,”C:\Windows\Microsoft.NET\Framework\v4.0.30319”
The ”C:\Windows\Microsoft.NET\Framework\v4.0.30319” refers to the path of my .NET Framework 4 directory.

Source: http://research.microsoft.com/en-us/...t/ILMerge.aspx

I now have a single .EXE file that works on any computer with Windows and the .NET Framework 4.0 installed! Thank you guys very much for all of your help!