Interop

[Guest]

My vb.net application uses a 3rd party dll. The dll uses an ocx. In order
for the ocx to register - the dll must be in the winnt directory. The
interop for the application copies the dll to the winnt/system32 directory.
This cause the ocx/dl to fail.

Is there any way to force the Interop to leave the dll in the winnt dir?

thanks
eveready

 

[Crouchie1998]

Obviously, it will fail if its registered in one directory & its moved to
another directory & not re-registered.

Have you written then DLL that your application uses?

Crouchie1998
BA (HONS) MCP MCSE