Hi,
I have the following problem: we have our application spread over two folders
Folder1:
main.dll (managed cpp assembly, strong named)
... many many resources for main.dll
Folder2:
user1.exe (references main.dll, C#)
user2.dll (references user1.dll and main.dll, C# class library)
I provide a user1.exe.confi g file in Folder2 which uses the codebase tag to
give the user1.exe the path to main.dl.
This works well, BUT when user2.dll is loaded by user1.exe, it does not find
its dependent assembly main.dll.
I also tried to give the user2.dll a config file, but this is not used by
the framework. What am I doing wrong?
It seems to me as if only the first dependency level is redirected by the
codebase tag and not the second one.
We do not want to copy the main.dll to folder2, because it has a couple of
unmanaged resources which are located relative to main.dll
Is the procedure to use a config file suitable for this problem, or is there
any other possibility for such a scenario?
I have the following problem: we have our application spread over two folders
Folder1:
main.dll (managed cpp assembly, strong named)
... many many resources for main.dll
Folder2:
user1.exe (references main.dll, C#)
user2.dll (references user1.dll and main.dll, C# class library)
I provide a user1.exe.confi g file in Folder2 which uses the codebase tag to
give the user1.exe the path to main.dl.
This works well, BUT when user2.dll is loaded by user1.exe, it does not find
its dependent assembly main.dll.
I also tried to give the user2.dll a config file, but this is not used by
the framework. What am I doing wrong?
It seems to me as if only the first dependency level is redirected by the
codebase tag and not the second one.
We do not want to copy the main.dll to folder2, because it has a couple of
unmanaged resources which are located relative to main.dll
Is the procedure to use a config file suitable for this problem, or is there
any other possibility for such a scenario?