. ...">

How to make ActiveX COM object work in IE 64 bit?

I have a COM object embedded in an ASP.NET page using <object classid="clsid:XXX...">

. It works in IE 32 bit but doesn't work in IE 64 bit - can't access its features. No error messages, no event logs where I can get some information.

dll is in C #, includes a COM visible class, compiled for any CPU (although I also tried x86) and registered during client installation by executing regasm. This creates registry keys and everything works fine except IE 64. I searched the internet for the problem, or at least some advice, and I couldn't find anything.

I got a response on another forum, something about _MERGE_PROXYSTUB (I think this is a preprocessor definition?) And ProxyStubClsid32 registry key, but not very verbose. Well, I searched again, didn't find much, and experimented: Rebuilt with _MERGE_PROXYSTUB defined, created ProxyStubClsid32 keys everywhere, but no result.

What are at least possible solutions or points of view? Maybe there is a way to at least get the logs about why IE 64 can't access it?

+2


a source to share


1 answer


AnyCPU will work in a 64-bit program, but you have to register it differently. Use the 64-bit version of Regasm.exe, you will find it in c: \ windows \ microsoft.net \ framework64 directory. Make sure you get the keys in HKLM \ Software \ Classes \ CLSID and not HKLM \ Software \ Wow6432Node \ Classes \ CLSID.



+3


a source







All Articles