Explicit Paths for DLLs

[jumpingjack]

Hello,

I am using Labview 8.5

Now I have 2 C# Dlls which I use in my project in Directory A. I also have a copy of the 2 same dlls in Directory B. Now when I update the DLLs in

Directory A, If I am not mistaken Labview seems to be "smart" enough look for the dlls in Directory B and use them instead. Is there anyway

I can force the dlls to be loaded from a specified path & without having to redo my schematics for the updated dll?

C:\Labview\testing\DataInputEvent.vi
    - Expected Assembly "AppFW.Remote, Version=0.0.2854.18042, Culture=neutral, PublicKeyToken=null", but found "AppFW.Remote, Version=0.0.2852.29533, Culture=neutral, PublicKeyToken=null".
    - The .NET assembly expected to be at "C:\Labview\FullyFunctional\AppFW.Remote.DLL" was loaded from "C:\Labview\testing\AppFW.Remote.DLL".
    - The .NET assembly expected to be at "C:\Labview\FullyFunctional\RemoteTestClient.DLL" was loaded from "C:\Labview\testing\RemoteTestClient.DLL".

[Jason_Whaylen]

Hi jumpingjack,

Thank you for contacting National Instruments.  From the information you provided it looks like there are two things to consider.  If you are looking to force the DLLs to be loaded from the specified path, one of two things can be done.  If you move the additional copy of this DLL outside of the LabVIEW directory it should not automatically locate it when it is searching for the specified DLL.  Also, it looks like the name of the DLL is the same, but in a different folder.  By changing the name of the file, even if it is in its current directory, it will not be linked to the file which has the specified path.

I hope this helps!  Let me know if there is anything else I can help with or clarify.  Have a great day.

Jason W.