Very Computer

Hi,

I have a .NET assembly that needs to be used by VB6. Using regasm /tlb
registers it. However, when running the code, the .NET dll cannot be found.
If I put it in the GAC - then of course it finds it. However, I want to know
why it doesn't.

Using filemon, it seems that the runtime is trying to find the assembly in
the system32 folder - not the folder where it was registered from. This
seems to be the problem - and of course putting it in the GAC, places it in
a known location where it can be found. How can this default behavior of
looking in system32 be changed so the GAC can be avoided?

Thanks

You can put the file in the same folder as the EXE is running in, in the
GAC, or use regasm.exe with the /codebase switch.

David Stucki
Microsoft Developer Support

This posting is provided "AS IS" with no warranties, and confers no rights.

This file is being executed by another DLL, not an exe. Putting it in the
same directory does not help, using filemon shows the runtime is looking for
the file in system32.

The GAC is what I was trying to avoid.

I think the codebase option is the way to go - didn't see it before. Thanks!

Quote:> You can put the file in the same folder as the EXE is running in, in the
> GAC, or use regasm.exe with the /codebase switch.

> David Stucki
> Microsoft Developer Support

> This posting is provided "AS IS" with no warranties, and confers no
rights.

The file has to be in the same directory of the process that hosts it. If it
is executed by a DLL, then it has to be in the same directory of the EXE
that hosts the DLL. (This is the reason why you have to put the file in the
directory of VB.EXE when you debug the file from inside the VB IDE.)

As David pointed out, the better option would be to use /codebase, or put it
in the GAC.

Hope this helps.

Thanks,
Santhosh
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
?2002 Microsoft Corporation. All rights reserved.