ASP.Net DLL Reference Search Paths?

[Chris Ashley]

I have a managed C++ wrapper which is referencing an unmanaged C++ DLL.
How can I modify the reference search paths for ASP 2.0 so it can find
the unmanaged DLL? It copies the managed DLL okay, but can't find the
unmanaged DLL ('the specified module coult not be found'). It only
seems to work when I place the unmanaged DLL in the System32 folder.
Doesn't work in the project root, solution root, or bin directory.

[Cowboy \(Gregory A. Beamer\)]

Unmanaged COM DLL or unmanaged native DLL?

COM requires a COM wrapper. For native, you will have to set up a proper
declaration (Pinvoke.com shows how to do this for WinAPI calls). The norm is
the System32 directory, but, if I remember correctly, you can path a native
DLL in the declaration statement.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com

*************************************************
Think outside of the box!
*************************************************
"Chris Ashley" <ch***********@gmail.comwrote in message
news:11**********************@f16g2000cwb.googlegr oups.com...

>I have a managed C++ wrapper which is referencing an unmanaged C++ DLL.
How can I modify the reference search paths for ASP 2.0 so it can find
the unmanaged DLL? It copies the managed DLL okay, but can't find the
unmanaged DLL ('the specified module coult not be found'). It only
seems to work when I place the unmanaged DLL in the System32 folder.
Doesn't work in the project root, solution root, or bin directory.