.NET 3rd Party Control Licensing in LabVIEW via .licx file

[Anthony_L]

Hello:

This support question is about LabVIEW recognising the *.licx file used in modern .NET control registration after purchasing a license. Apparently, my LabVIEW does not seem to recognize licensed .NET controls.

Here is the story:

=============

I was testing the trial version of a .NET control --specifically the vsFlexGridClassic.Net control by ComponentOne (or GrapeCity). And after being satisfied that the control worked well and met my needs, I went ahead and paid for a license to activate the .NET control and thereby get rid of the nagging screens from the trial license.

But right after activating the license via a special licensing control panel, LabVIEW continued to show the nagging screen that the control was un-registered (non-activated) and that I needed to call and buy a license for it  from the vendor (which I already did).

I contacted ComponentOne support staff who, via remote desktop access, verified that the license was valid (recognized) if the control was used in the Visual Studio IDE. And thus concluded that the problem is with LabVIEW.

I tried the .NET control with Activation on LabVIEW 2020 and the same problem persisted where LabVIEW would not recognize the control as being registered, and would throw that trial dialog; and this time with note that the trial had expired.

Question on .Licx File and LabVIEW

--------------------------------------------------

ComponentOne tech support informs me that the .NET controls have a new licensing method that uses a .licx file for component registration (after purchasing a license), and it is their observation that the nagging dialog was because LabVIEW does not recognize the newer licensing method, via .licx file, used by contemporary.NET controls.

is the above observation True?

How can we make LabVIEW recognise licx file for component registration?

Anthony

[billko · Accepted solution]

It's not really even new.  (I've seen references to licx files since 2008.)  Sorry, I have nothing.

[Anthony_L]

Thanks billko:

I went ahead and tried another .NET control from the licesensed suite of controls and those other controls did not flag the trial dialog warning. So it seems that the licensing issue is specific to the one .NET Control that I needed to use.

I have reported this to the Vendor and they are looking at it.

No wonder there were no hits when searching for issues with LabVIEW recognizing .NET licenses controls.

So this problem is indeed SOLVED! In that it is not a LabVIEW issue.

Take-Away from This:

================

Always be sure to check with vendor's other controls to see if those ones also throw the trial license dialog. If Not then, the issue may very well be that the .NET Control vendor is not propagating the license to cover ALL controls in the suite.

See screen shot of .NET control that runs OK and the lower one that fails to load from the same vendor's suite.

Thanks Again billko

Anthony L. 

[billko]

Mark YOUR post with the info on how you fixed it as the solution, not mine.  🙂