I have some question about changing location of referenced DLL.
I have a solution with 7 projects. One of the projects (let’s call it ProjectA) uses an xxx.dll that is NOT .NET dll (it’s a dll of Java code, created by JBNBridge). Xxx.dll was added to the project using “Add”->”Existing Item”. Everything worked well till I got a requirement to hold all dlls in a separate external directory. I removed the dll item from the project, then I moved the dll file to the external directory and in the end I added the dll item from the external directory checking that the dll’s “Copy to Output Directory” label has value “copy always”. I rebuilt the project – successfully.
The compilation succeeded. BUT, when I run my project, I receive an unhandled JNBridge exception just in line I try to create an object from the dll.
When I returned the dll to his old place – the runtime exception continues to appear.
I have a solution with 7 projects. One of the projects (let’s call it ProjectA) uses an xxx.dll that is NOT .NET dll (it’s a dll of Java code, created by JBNBridge). Xxx.dll was added to the project using “Add”->”Existing Item”. Everything worked well till I got a requirement to hold all dlls in a separate external directory. I removed the dll item from the project, then I moved the dll file to the external directory and in the end I added the dll item from the external directory checking that the dll’s “Copy to Output Directory” label has value “copy always”. I rebuilt the project – successfully.
The compilation succeeded. BUT, when I run my project, I receive an unhandled JNBridge exception just in line I try to create an object from the dll.
When I returned the dll to his old place – the runtime exception continues to appear.
Can you advise me what to do? Is it a rule about how can a dll been transferred to a separate directory? Is it important this is a referenced dll or not .NET dll?
Thank you.