We have a .NET assembly (C++/CLI) that has been installed for COM interop on a remote machine which we basically use as a file server. The assembly is strong named. The directory on the server where the assembly is installed also contains MFC dll's which are linked with the .NET assembly. On a workstation we have used regasm to register the assembly to the mapped drive where the assembly is found. Now when we run a test app (C#) which runs through some VB6 modules that instantiates object the assembly we get an error that it cannot find the file specified.
I ran fuslogvw.exe to see what was going on with the load of the assembly and it looks like it is only probing the directory where the test app is installed. It does not know to look where we registered the file.
One thing to note is that when everything is run on the same machine we don't have any problems. The test app and the assembly are still in different directories but it works.