Hi

I have run into a problem using ZeroDeployment.

I short, IEExec loads a VB application, which uses a DLL
written in C++. VB calls into managed C++ code. The
managed C++ code calls into unmanaged C++ code. So far, no
problem. But when the unmanaged C++ code does a
CreateThread, the error System.DllNotFoundExecption is
thrown.

Creating our own 'Application loader' can load the VB
application and everything works.
Using calls like:
       da = [Assembly].LoadFrom(URL)
       dt = da.GetType(ClassName)
       sc = Activator.CreateInstance(dt)
       sc.Show()

Note, while testing, the VB application have been fully
trusted.

A search on the net gave little result, though I did find
a communication which seemed to be in the vicinity of my
problem (Actually I think it is the same):

-- Extract start --

The bug is inside of the .Net Framework (CLR). IIS6 is
doing its part
correctly, VC++ is compiling and pulling in CLR correctly,
but CLR is
bugging out about the name of the DLL that IIS6 gave it.  
The bug can be
independently reproduced outside of IIS, so it's a CLR bug.

Unfortunately, the IIS team is having a hard time
convincing the CLR team to
fix/resolve this issue, but we're working on it.  If you
can help us make a
case on the importance of using managed extensions
directly in ISAPI, please
do. :-)

-- Extract end --

Is it a bug?
Isn't is supposed to work (unmanaged code ZeroDeployed)?
Is it something that could find its way to the
KnowledgeBase?
(It isn't Superman!)

Regards
 Tommy