Currently when binding a .Net Constructor node to a private assembly the vi saves the absolute path to the assembly. This behavior causes a lot of pain when multiple developers working on the same project have the source code repository mapped to different local directories. Every time I load a project I go through several iterations of Labview/.Net searching for the "missing" assemblies. Depending on what I have on my disk at the moment, oftentimes it will bind to a dll that's in a completely different project.** Trying to find a workaround for those vendors who refuse to put their assemblies in the GAC has been problematic.
Note I'm not asking for a path input to the .Net Constructor node. I just want the option for the path to be stored internally as a relative path rather than an absolute path.
**This is a little odd given private assemblies aren't supposed to be loadable outside of the given .Net AppDomain. I guess there's not a 1:1 correlation between Labview app domain and .Net AppDomain?
