So I'm looking for one of a few various solutions...
Creating a packed library that has .net calls that link to a specific path for the .net dll... the problem being when you build it relinks to the local copy it creates...
It'll eventually find the dll in the original path you specified but depending on how you call the LV VI this may or may not work (when calling from various forms of test stand)...
Can I create a .net config file for the lvlibp file that points it to a set dll?
I tried using the .net config files and couldn't get them to work in the basic functionality even on a built executable... I have two versions of the dll I would install into the GAC and then have the config file have a binding redirect such as in the documentation to the new version... the executable when the old version was installed into the gac would work fine no matter what you put into the config... I'm fine with that... but when I installed the new version of the dll and removed the old, the executable would break not being able to find the dll even with the correct redirect syntax in the application name.exe.conf file residing in the same directory.
http://zone.ni.com/reference/en-XX/help/371361K-01/lvhowto/net_specifying_assembly_version/
Anyone have any further thoughts/info/etc on using .net dlls and being able to update them independently of your TS or LV code and being able to link them to a given path vs having LV builds suck them into obliviion..
I have to do builds because the system will normally be running LVRT.
Thanks,
Michael