c# - unable to properly register x64 COM dll on windows 7 x64 -


Text after "itemprop =" text ">

, dll is being consumed by applications created for .NET 4.0 x86 I have a C ++ ATL COM DLL that is original The form was created for x86, everything works fine

Recompiling COM dll for 64, and then using it after entering c:. \ Windows \ system32 \ regsvr32 (Un after reg 86 dll), I want to fail or COM DLL reference window in Visual Studio, I HKCR with 64 and x86 versions of registered dll and HKLM \ Softwares For reg key is exported, and no keys are missing, the corresponding key pointing is the correct dll location.

Additionally, after registering the 64 dll, I am able to add the folder where the file is located, and by selecting it in the context of the Dll, but it still does not execute (.net assembly error 64 with the following) is set to

System.Runtime.InteropServices.COMException (0x80040154): COM class factory for component with CLSID is gaining {00000000-0000 -0000-0000-A797AD238051} Father Flow NG Fluctuations due to error: 80040154 Category Registered Exception is HRESULT (0x80040154 (REGDB_E_CLASS NOTREG)). System Prkrnttaim Taiphandlekret instance (runtime type type Boolean public only Bulia N No. Czech systems, Boolean and Kabac, Runtimemahandl Inariyl and Sitior, Boolean and Bianids Security Czech). In the system Runtime type Create Instance Slow (boolean public bus, Boolean skip check, Boo Lean Philcapes) on system. RuntimeType.CreateInstanceDefaultCtor (Boolean publicOnly, Boolean skipVisibil ityChecks, Boolean skipCheckThis, Boolean fillCache) (type on System.Activator.CreateInstance, Boolean nonpublic)

I spent looking for considerable amounts of time Is online, but nothing is found from the far, anybody seen by anyone in this way or a debugging tool that I might use?

I do not own Dell, which he owns, can see x64 DLL made on the machine, but has tried on 2 other machines, and it does not work on any one.

This question is outdated, and I will need more information in it, however, completely troubleshooting May be able to provide some tips for anyone running on the same issue.

Given that you regsvr32 are used, DLL is saying something mean that DLL called extra work on your own Windows registry in an exported function Has been doing. As you might think, registry entries are different between x86 and x64, but this is not necessary for your basic problem. You can and often, both x86 and x64 type libraries should be registered.

How is a specific type of library registered? This is a way to check the tool. The same information is in the registry, but this tool can be quite friendly. The device visual studio must be in the path set from the command prompt. It seems that the error is a GUID given about a class, which you can check with object classes - & gt; All things in the tree:

Finding a Class in a Tree

If you have to be a class (you may have to re-register the x86 version to check), you can get the information on the COM interface that you just found by expanding the entry for the GUID to class tools Can interface. If there is a type of library, then it should be said. Note that TypeLib information can have both win32 and win64 entries for the path:

 interface both Win32 and win64 path example

without more information, it is hard to say, but I think that something is wrong X64 For self-registration and / or type libraries by chance, the libraries you plan to make a living, you can not trust yourself registering anyway - the installer packages can make your own registry entries. If you have more information, then I can try to provide more information.

Comments

Popular posts from this blog

Python SQLAlchemy:AttributeError: Neither 'Column' object nor 'Comparator' object has an attribute 'schema' -

java - How not to audit a join table and related entities using Hibernate Envers? -

mongodb - CakePHP paginator ignoring order, but only for certain values -