Measurement Studio for .NET Languages

cancel
Showing results for 
Search instead for 
Did you mean: 

Measurement Studio 2013 for VS 2013 C# WPF Error: XamlParseException occurred

Hi,

I installed Measurement Studio 2013 on Visual Studio 2013. I followed "How to add tool box for VS 2013 instruction".

Winform Applications run great! No problem at all.

My VS2013's tool box shows two icons (one in black&white and the other in color) for each NI Measurement Studio 2013's UI element.

All of WPF applications shows error during running after successful compiling. Any Measurement Studio UI element (LED, Gauge, Graph.....) make error that reads "XamlParseException occurred".

"Additional information: 'The invocation of the constructor on type 'NationalInstruments.Controls.LED' that matches the specified binding constraints threw an exception.' Line number '7' and line position '10'."

 

 

LED_Error_in_WPF.JPG

Does anybody run MeasurementStudio 2013 in WPF of VS 2013 successfully? Any solution?

 

 

 

0 Kudos
Message 1 of 4
(5,405 Views)

Hi yparkway,

 

Can you post the clipboard contents after selecting the Copy exception detail to the clipboard option in the exception dialog?

 

Thanks,

Daniel Dorroh
National Instruments
0 Kudos
Message 2 of 4
(5,388 Views)

Hi yparkway,

 

It looks like this issue might be related to not having created the correct .licx file. I know you went through the Using Measurement Studio 2013 for Microsoft Visual Studio 2013 KnowledgeBase article, but you may have over looked the "Using Measurement Studio 2013 User Interface Controls and Analysis .NET Class Libraries in Visual Studio 2013" section, where it links how to create a license file. The link to this file can also be found here: http://zone.ni.com/reference/en-XX/help/372636F-01/mstudiowebhelp/html/licensingnetwithoutintegratio...

 

We were able to replicate a similar error and creating and installing the .licx file seemed to resolve the issue. If this doesn't help, please let us know!

Rachel M.
Applications Engineer
National Instruments
0 Kudos
Message 3 of 4
(5,374 Views)

If you click on "View Detail" in your screenshot and look at the inner exception, that's where you'll actually find what went wrong. If it is a licensing issue, then you'll see something like

 

Inner Exception     {"NationalInstruments.Controls.Internal.WpfStandardLicenser is unlicensed."}

0 Kudos
Message 4 of 4
(5,332 Views)