I am trying to interface with a proprietary .net dll. The problem I am having is that this dll can be in multiple places and may not always be in one location. This means that when I open a VI that tries to link to the dll and it is not in the correct location, the VI throws warnings that I don't want my users to ever see. The NI help that I have seen makes it clear that when the VI is opened any .net assemblies referenced are loaded.
I have tried breaking the portion of the VI that interfaces with the dll in to a sub VI and then trying to dynamically load it after checking that the dll is present in the expected location. I have tried "dynamically loading" and and "call by reference", "Call by reference" does not work as it still tries to load the .net assembly no matter what the "call setup" settings are. Dynamically opening the sub VI seems to work in the sense that if the sub vi references a bad dll location, the caller does not fault unless it is run. However, I am also trying to manage some .net references which seem to be dropped in the dynamically called sub vi. I have tried using global variables to hold the references as well as doing a "get value" from the upper level VI.
I am not real familiar with the .net world and would appreciate any pointers you can give me.
