Registering DLLs

It worked fine on the old server...

[garann]

Hello,

I've got a DLL my application needs to use. The application just moved from a development server to the server I'm going to deploy it on, and it works until it tries to use a third party DLL I purchased. I thought I only needed to drop the DLL in the bin folder to have the server recognize it - is this incorrect?

The error message I get is:

[b]System.Runtime.InteropServices.COMException: COM object with CLSID {BF18F2A7-8B30-11D3-A95C-00008639BD6E} is either not valid or not registered.[/b]

What do I need to do to make it work?

Thanks in advance,
g.

[korkus2000]

Drop it into the assemblies folder either under the windows or wnnt folder. This should register it with the GAC.

Are you running .Net?

[garann]

Ok, I copied it into C:\WINNT\assembly and it shows up just fine. I restarted IIS, but still the error remains.

I am using .NET - do I need to put the DLL somewhere else?

[korkus2000]

What kind of .Net app are you using, webservice, aspx, or program, that is calling the DLL?

[garann]

It's a web application/aspx.

[korkus2000]

Have you tried using the add assembly tag in the web.config?

[garann]

I just tried. It says it can't find the DLL.

[korkus2000]

You probably need to contact the dll distributer. I am out of ideas.

[garann]

Well, thanks for giving it a shot!

[WebJoe]

try in the command line

regsvr32 c:\pathtodll\dllname.dll

that usually fixed all problems I ever had with libraries

[garann]

I tried that command, and I get this error:

F:\pathToDLL\myDLL.dll was loaded, but the DllRegisterServer entry point was not found.
DllRegisterServer may not be exported, or a corrupted version of F:\pathToDLL\myDLL.dll may be in memory. Consider using PView to detect and remove it.

I should point out that it shows up in the global assembly cache, and that when I tried to use the command pointing there, it couldn't find the DLL. So I pointed at the bin folder of my virtual directory.

Oy.. What I wouldn't give some days to go back to Java.. Thanks anyway for the tip. :)

[WebJoe]

sounds like the dll depends on some other libraries that are not where they are expected...had the same problem (and the same err-msg) with an installation of oracle ado libraries.