Hi,
We were developing projects targeting to .Net 4.6 using Measurement Studio 2015, and everything was working fine - the projects were built successfully with both Visual Studio 2017 and Jenkins( which uses MSBuild building the same solution files as VS2017).
But as soon as we migrated our projects to .Net 4.7, Visual Studio 2017 build worked fine as usual but Jenkins build started popping up with 'NI assemblies unlicensed' error messages to all the NI assemblies that are referenced in the projects. The Visual Studio and Jenkins were building exactly the same solutions with exactly the same license file configurations. But why only Visual Studio worked? I was wondering if there are some NI license caching somewhere that Jenkins could probably looking for? If so, I can do a cleaning up of all the NI license caching so that Jenkins can pick up the right information? And after rolling back the pc to previous restore point, everything worked again.
I am not discussing about Jenkins build, but I would like to know if NI caches license information somewhere? Or how does NI do licensing during compile?
Thank you very much,
OxTS software team
