IIS7 - Extensibility

Re: ISAPI DLL call .Net DLL

lextm — Wed, 29 Apr 2009 02:29:46 GMT

How did this standalone application calls this .NET assembly? Also via COM interface?

If you add this .NET assembly as reference of this app, or the app uses reflection to load it, then the VB script test is still a must to narrow down the problem.

Re: ISAPI DLL call .Net DLL

brusoft — Tue, 28 Apr 2009 13:02:08 GMT

I did the above without the /codebase /tlb and then did a drag-n-drop to the windows\assembly (GAC). I don't have a VB Script, but I do have another stand alone application that has no problem calling the .NET DLL.

Re: ISAPI DLL call .Net DLL

lextm — Tue, 28 Apr 2009 05:48:31 GMT

Do you use the following command line to register this .NET assembly?

regasm netdcom.dll /codebase /tlb

where netdcom.dll is the file name.

If you already did that, can you write a VB script to call this COM locally?

ISAPI DLL call .Net DLL

brusoft — Tue, 28 Apr 2009 02:17:19 GMT

I'm getting an OLE System error that file can't be found when my ISAPI DLL trys to call a .NET DLL. This is occurring on a new installation running Server 2008 and IIS 7. The same ISAPI DLL and .NET DLL are communicating fine within the other installation running Server 2003 and IIS 6. I first had difficulty with the 2003/IIS6 installaction until I registrered the .Net DLL with regasm.exe and installed the .NET DLL in the c:\windows\assembly (GAC) folder. I've done the same with the new installation, but get the above error. Any ideas what I'm missing?