C
Chris S. Hogan
Guest
If this is an old COM .dll and not a .NET assembly you might try regsvr32 to register the .dll manually and have its classes available. Details here: http://support.microsoft.com/kb/249873 From: oedev [mailto:bounce-oedev@progress.com] Sent: Friday, February 28, 2014 2:54 AM To: TU.OE.Development@community.progress.com Subject: Assembly (dll) related questions Assembly (dll) related questions Thread created by oedev Hi I'm trying to get OE 10.2B to recognise an assembly, but not with much luck. I am working with a number of dll's from a particular company, which all work fine. However, one particular assembly will just not be recognised by OE. 1. I normally add my assemblies to the GAC using gacutil. When I try to add this assembly to the GAC, I get the error; Failure adding assembly to the cache: Attempt to install an assembly without a strong name which I believe is related to the fact that the assembly is not signed ? 2. If I copy the assembly into my project folder, and add it to my projects assembly references, then this works. However, none of the available classes in the assembly are exposed. In the class browser, the assembly has a red cross against it, and the following text is displayed; Assembly Accusoft.Forms1 Location: Accusoft.Forms1, Version=1.0.2.30, Culture=neutral, PublicKeyToken=null Note: This assembly is not available to the Class Browser. The assembly could not be loaded from the global assembly cache or from the assembly directory of the project. Again, Is this because it is not signed, indicated by the publickeytoken=null ? 3. The suppliers of the assembly actually provide the code as well. I have looked at the build parameters for the assembly, and noticed the "Register for COM Interop" option is not set - is that significant ? Any advice/help will be much appreciated! Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...