I have a ASP.NET Web service that runs under IIS. The moment I add a dll
to the bin folder and try to Browse the Web Service from IIS (or from any
other place), I get an indefinite Waiting for <name>... and the service is
not invoked correctly.

The dll that I am adding is a .NET dll that has some Win32 dll
dependencies. I am assuming that the problem has to do with a problem
loading the dependency dlls but I have no way of knowing for sure. I copied
the Win32 dlls to both Windows\System32 and Windows\System32\inetsrv but I
am not sure if the problem might have to do with dependent dlls of these
dlls (such as msvcrt.dll and so on).

If I then remove the dll that is causing the problem I need to restart IIS
in order to be able to browse the service again.

Any idea what might be the problem an how to solve it?

Thanks,
Jeronimo

Re: Problem adding a dll to a Web Service by David

David
Sat May 10 23:29:34 CDT 2008

On May 10, 8:28=A0pm, Jeronimo Bertran
<jeronimo.bert...@newsgroup.nospam> wrote:
> I have a ASP.NET Web service that runs under IIS. =A0 The moment I add a d=
ll
> to the bin folder and try to Browse the Web Service from IIS (or from any
> other place), I get an indefinite Waiting for <name>... =A0and the service=
is
> not invoked correctly.
>
> The dll that I am adding is a .NET dll that has some Win32 dll
> dependencies. I am assuming that the problem has to do with a problem
> loading the dependency dlls but I have no way of knowing for sure. I copie=
d
> the Win32 dlls to both Windows\System32 and Windows\System32\inetsrv but I=

> am not sure if the problem might have to do with dependent dlls of these
> dlls (such as msvcrt.dll and so on).
>
> If I then remove the dll that is causing the problem I need to restart IIS=

> in order to be able to browse the service again.
>
> Any idea what might be the problem an how to solve it?
>
> Thanks,
> Jeronimo


Use ILDASM.EXE on the managed assembly DLL that you are adding to
identify its dependent managed assemblies. If some of the managed
assemblies are merely proxy stubs that require Win32, you will see
that in the stub assemblies as you drill into it, and you can chase
down that DLL's native code dependencies with...

Use DEPENDS.EXE on any native code DLLs that are involved to identify
its native code dependencies. If some of the native code are merely
proxy stubs to managed code interop DLLs, you can observe that and
chase it down with ILDASM.EXE.

You can also use REFLECTOR.EXE for the managed assembly.

It sounds like you have a managed assembly which is dynamically
loading (and failing) some other assembly. Since the initial assembly
is already loaded and cached, you will need to restart its containing
Application Pool to clear it out of memory. If this is IIS5, you can
also recycle the aspnet_wp.exe containing the cached managed assembly.
You should *never* need to restart IIS when dealing with managed
code.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//