Make Win32 MC++ assemblies works under Win64

[Jerome]

Hi all,

I've made a .NET wrapper of a C++ toolkit using MC++ (perhaps I should now
take a look to C++/CLI).
The 32 bits version works fine on Win32 and 64 bits version works fine on
Win64 .... but .... 32 bits version fails to run under 64 bits (the C++ 32
bits version works well).
In fact a FileNotFoundException is thrown at startup ... no way to get rid
of it !

I suspect it could not work (my little finger tells me) ... I found no
relevant information about this behaviour.

What do you think ? A problem with manifests ?

..NET Framework 2.0
Visual 2005
Winxp 64

Best Regards
Geronimo.

 

[jacky kwok]

Hi all,

I've made a .NET wrapper of a C++ toolkit using MC++ (perhaps I should now
take a look to C++/CLI).
The 32 bits version works fine on Win32 and 64 bits version works fine on
Win64 .... but .... 32 bits version fails to run under 64 bits (the C++ 32
bits version works well).
In fact a FileNotFoundException is thrown at startup ... no way to get rid
of it !

I suspect it could not work (my little finger tells me) ... I found no
relevant information about this behaviour.

What do you think ? A problem with manifests ?

.NET Framework 2.0
Visual 2005
Winxp 64

Best Regards
Geronimo.

The application runs understand 64 bit windows must be pure 32 bit or
pure 64 bit.

That is
if the main application is 32 bit executable, then all the other
components (DLLs etc) must be also 32 bit.

if the main application is 64 bit executable, then all the other
components (DLLs etc) must be also 64 bit.

Then, if the the main application is 64 bit executable, it cannot load
32 bit DLLs.

Hence, if the DLL is pure dotnet (e.g. created by C# with AnyCPU
setting), it can be used in both 32bit and 64 bit.

However, for MC++, it is very possible it will be linked with native API
function and the DLL will be used under 32 bit or 64 bit only.