From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
When building a .NET interop assembly in Labview, the four digits of the assembly version are defined as "Major", "Minor", "Fix", "Build". This does not comply with the .NET assemly version scheme.
Nevertheless, NI Measurement Studio assemblies are versioned the correct way, e.g. "NationalInstruments.Controls, Version=15.0.45.3898" complies with "Major", "Minor", "Build", "Revision".
My final question is: What is NI's understanding of the digits of a .NET assembly version?
In LabVIEW this version information terminology is used to comply with the generic LabVIEW build specifications and not necessarily directly with the .NET assembly version scheme. This terminology is common across all LabVIEW builds such as Installer, EXE, DLL etc.
For example there is a VI called "Set Build Specification Version" that programmatically sets the version information of a build specification. It would be inconvenient and unpractical to provide a similar VI just for .NET assembly; this might be the rationale behind this standardization, perhaps.
