What prevents me from running my .NET 2.0 application on a 64-bit platform?

Question

I have a .NET 2.0 application that will not work on a 64-bit OS (the client tried both Server 2003 and Windows 7). Error message:

The application failed to initialize correctly (0xc0000135).

Including this message returns little useful information ( one link I just said that if you receive this message because they do not support 64-bit).

I would like to enable 64-bit support in my application. I do not have a 64-bit system for testing, and I do not want to make this investment without having an idea of ​​what is required for this work.

Does anyone know what this error code means? Are there any common errors in 64-bit support that I should pay attention to?

The only thing I have is the .NET TAPI shell (now an outdated product called TransPort), it may not work on a 64-bit system. (The provider is long gone, and I do not have the source code).

Answer 1

The most likely cause of this problem is that your code uses a 32-bit specific native DLL through COM interoperability, mixed-mode assembly (e.g. C ++ / CLI), or through PInvoke. Try setting up your .Net application as specific to the x86 architecture and see if it works.

corflags, 32-

• http://msdn.microsoft.com/en-us/library/ms164699(VS.80).aspx

Answer 2

, JaredPar, Interop, Microsoft FxCop , 32/64 DLL (System32.dll User32.dll)