Calling VB.NET DLL from VB6

[Mauro]

Hi,

We' ve encountered a problem relating to IIS6.0 isolation mode settings on
our new Windows 2003 web server.

Our architecture is the following
1) Web application written entirely in ASP. This app carries out all data
access through a VB6 DLL.
2) We recently added a new .NET DLL to save files uploaded by the ASP into
the database, and then copy the file to a directory used by Index Server.
This .NET DLL is registered using regasm which also creates a type library
file.
3) Under our old web server - Windows 2000 - it all runs OK.
4) In the new web server, we've discovered that we need to set the IIS5.0
isolation mode and it all works fine when running from a browser.
5) In the new web server, if we set the IIS6.0 isolation mode the VB6 DLL
fails immediately as soon as it tries to invoke the type library when
running from a browser.
6) In the new web server, if we set the IIS6.0 isolation mode and run a .NET
test application as a user belonging to the Administrator group, it all
works fine.

We would really be interested in knowing if anyone else has come across
this, and hearing a sensible explanation for it. To us it doesn't make sense
that we are running any ASP.NET process given that the web client is an ASP
application.

 

[Cor]

Hi Mauro,

I think you find faster someone else when you post this also to the
newsgroup

microsoft.public.dotnet.framework.aspnet.

I hope you get your anwers.

Cor