Subject: Programmatically Check NI License
In-Reply-To: <AT5PR8401MB089811F14E226E3D6A1AF6F8CAB59@AT5PR8401MB0898.NAMPRD84.PROD.OUTLOOK.COM>
References: <0d6b01d6f9a7$e205e4a0$a611ade0$@solidusintegration.com>
<7CD01CAD-CA2F-4F0C-AA85-12640C46B9B1@ni.com>
<AT5PR8401MB089811F14E226E3D6A1AF6F8CAB59@AT5PR8401MB0898.NAMPRD84.PROD.OUTLOOK.COM>
Message-ID: <0d8301d6f9e1$b222a0e0$1667e2a0$@solidusintegration.com>
Dave,
Just tried that using "Get Installed Software.vi" that calls "Get Software
Details.vi" with added "isAvailable" output as you suggested. This output
returns "1" for both licensed and unlicensed software packages :(
Sergey
-----Original Message-----
From: Boyd, David J [mailto:david.boyd1 at abbott.com]
Sent: Tuesday, February 2, 2021 18:25
To: sliberman at solidusintegration.com
Cc: Info-LabVIEW
Subject: RE: RE: Programmatically Check NI License
Sergey,
I haven't been able to test this (when I query my system, I can't find any
components listed that I know are installed but unlicensed), but I noticed
this when browsing the library code:
In the nisyscfg project library, the Get Software Details.vi calls the
shared library function "GetSoftwareItemProperties"... and there's a
function output (not brought out to the caller) labeled "isAvailable"
(second-to-last param). Wonder if that returns a value you might use to
determine if a component is licensed/activated?
In these sorts of cases I usually end up making a copy of the call chain so
I don't disturb anything released in <vi.lib>.
Dave
-----Original Message-----
From: Info-labview info-labview-bounces at lists.infolabview.org On Behalf Of
Joe Friedrichsen
Sent: Tuesday, February 2, 2021 5:37 PM
To: sliberman at solidusintegration.com
Cc: info-labview at lists.infolabview.org
Subject: Re: RE: Programmatically Check NI License
EXTERNAL EMAIL: Only click links or open attachments if you recognize the
sender and know the content is safe.
> Calling "Get Installed Software.vi" and filtering its output for
> "NI Vision Runtime" gives me the package's description, ID
> and version number, but not the state of its license.
That's a surprise for me :-\
I'm not familiar with the vision modules and libraries, but maybe like
vi.lib, there's an llb or folder with VIs that aren't on the palette.
Joe
_______________________________________________
Info-labview mailing list
Info-labview at lists.infolabview.org
https://urldefense.com/v3/__http://lists.infolabview.org/listinfo.cgi/info-l
abview-infolabview.org__;!!BBM_p3AAtQ!Yut43HKHvjJbwrMM3kEShB-0LcsaFcCO65P-Vd
ytbjrZnnjnx_U4F3-r2HJJgEvEWGI$