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.

Measurement Studio for .NET Languages

cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to build C# application with NI NetworkVariables in VS2015/Windows 10

I am not able to build an application in VS2015 which refers to NI NetworkVariables.

 

An issue similar to this unresolved topic:

http://forums.ni.com/t5/Measurement-Studio-for-NET/LC-exe-crash-with-code-2146232797-when-compiling-...

 

Please see attached screenshot.

 

What can I do to fix this problem? Or will NetworkVariables never be supported more recent versions of Visual Studio (=later than 2013)?

 

 

 

0 Kudos
Message 1 of 3
(2,812 Views)

Hi there, 

 

 

Please check that you are definitely generating the right license files for your project according to the following document. It's important to specify the correct .NET and VS versions. (And I believe you'll need to select Network Variable Communication - this selector is multi-select however, so include everything necessary)

 

How Can I Create a .licx File for my Measurement Studio Project?

http://digital.ni.com/public.nsf/allkb/F96C8FE9AA34AFB886257F3D0021A4F1

 

After you have added these files and finishes building, if there is still an error relating to unlicensed assemblies, please refer to the following document.

 

Why Do I Get an Unlicensed Assemblies Error Message at Runtime When Using Measurement Studio .NET Controls in a Visual C++ Project?

http://digital.ni.com/public.nsf/allkb/53028D50C975D67286256DEF006FDB27

 

I hope this helps, best of luck with your application!

 

Sarah Flanagan

Applications Engineer 

National Instruments UK 

 

 

0 Kudos
Message 2 of 3
(2,772 Views)

Hi,

 

thanks for your quick reply! Although it did not solve the issue, it was good to learn a little bit more about the topic.

 

You will never believe what solved the problem, because it is simply too lame (which makes it kind of brilliant). One of the developers pressed "the button". The "Debug" button. The debug button in assertion dialog of the LC compiler error. It actually results in a succesfull build. When we then build again, the message no longer appears.

 

So god knows what really happened under the hood, but also on my PC, when I rebuild the solution, and press the debug button once. Nothing happens, except for that the build ends successfully. Every consequent build after that just runs fine.

 

Sometimes it's just doensn't make sense, but I don't really care :).

 

Hope this weird story also saves some time for somebody else (although that seems unlikely for some reason!)

0 Kudos
Message 3 of 3
(2,740 Views)