LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

When replacing a .NET assembly need to change LabVIEW code

Let me first say that yes, we know that there are problems with the versioning system of .NET and LV. We are making it better, but it is much more complicated than you would imagine at first. I've talked about some of this on my blog, so I would recommend check that out. But at the end of the day it is our responsibility to make this easier for you.
 
However, on this specific topic, my question is how is your assembly created? Is it a private assembly or a GAC assembly? Is it signed? These change the rules and behaviors of how things work in .NET and those ripple through LabVIEW.
 
The easiest way to work with constantly changing .NET assemblies is to use unsigned private assemblies (ie they are not in the GAC and are not digitally signed). This is the easiest system to work with in 7.x and works great in Constellation. If you are putting the assemblies into the GAC, I do strongly recommend holding the version constant. The .NET rules for binding to strongly named assemblies are much more strict and that makes working with them in LV more strict.
Message 11 of 11
(684 Views)