![]() | |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
If I change the MIDL/General/Target Environment to 32-bit then the DLL does show up under Add References of the c# project. Unfortunately this is not a solution since the DLL has to run as x64. Does anyone have any ideas as to how to solve this? |
#3
| |||
| |||
|
|
If I change the MIDL/General/Target Environment to 32-bit then the DLL does show up under Add References of the c# project. Unfortunately this is not a solution since the DLL has to run as x64. Does anyone have any ideas as to how to solve this? You need both versions of the DLL and you can register both of them as Win64 keeps a separate registry section for the WOW64 stuff. Visual Studio 2005 will only see the 32-bit version but when you run the app it loads the 64-bit version. Thanks for your response. We have solved it by adding the following |
#4
| |||
| |||
|
|
Thanks for your response. We have solved it by adding the following Post-Build-Event to my C++ project: tlbimp /machine:x64 "MyX64Com.DLL". This generates MyX64ComLib.DLL which enables COM interop between my C# program and MyX64Com.DLL. |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |