Invoking .NET DLL from ASP page

  • Thread starter Thread starter Ezhilan Muniswaran
  • Start date Start date
E

Ezhilan Muniswaran

Hi:

I have an ASP page that creates a VB dll which in turn calls a Class
Libraries created in .NET. This set up works fine in my development machine.
When I try to deploy this to the Web Server ( I installed the VB dll and
copied the Bin directory of the .NET class library into the Web Server and
also moved all the required ASP files). When I run the ASP page in the Web
server I get the following error

File or assembly name <NAME OF THE .NET DLL> or one of its dependencies,
was not found.
I created a Test VB Project and deployed that over to the Web Server to
instantiate the .NET DLL. The VB project works fine as long as the VB exe is
in the same directory as the .NET DLL(s). If I move the VB exe to another
folder I get the same error as above.

If any one knows what I am doing wrong here, please respond. Appreciate your
help
 
Ezhilan Muniswaran said:
Hi:

I have an ASP page that creates a VB dll which in turn calls a Class
Libraries created in .NET. This set up works fine in my development machine.
When I try to deploy this to the Web Server ( I installed the VB dll and
copied the Bin directory of the .NET class library into the Web Server and
also moved all the required ASP files). When I run the ASP page in the Web
server I get the following error

File or assembly name <NAME OF THE .NET DLL> or one of its dependencies,
was not found.
I created a Test VB Project and deployed that over to the Web Server to
instantiate the .NET DLL. The VB project works fine as long as the VB exe is
in the same directory as the .NET DLL(s). If I move the VB exe to another
folder I get the same error as above.

If any one knows what I am doing wrong here, please respond. Appreciate your
help
Click to expand...

So it's:
ASP > VB6 COM DLL > .NET DLL

..

Ok your .NET DLL is enabled for COM interop. A .NET dll registered for COM
interop will be found by the calling COM program only if the .NET DLL is:
1 in the local directory
2 in the GAC, or
3 registered with the /codebase option
eg
regasm myDotNetLib.dll /tlb:myDotNetLib.tlb /codebase

Options 2 and 3 require the .Net dll to be strong named.

David
 
Back
Top