In previous tutorials, we have created a package for our API. We created a palette; added examples, help items, and Tools menu items; included a licensing agreement; and defined our custom installation options. Now we will assume that we intend on selling our toolkit to LabVIEW users. When selling a toolkit, a common practice is to license your package to prevent unauthorized users from accessing the toolkit after an evaluation period. Using VIPM Free Edition, you can license a library using the NI Licensing and Activation Toolkit, documented here. Once you have a license file for your library, you can associate and include the license file with the package using VIPM. You can also bind the license file to the package using VIPM Pro Edition.
Note: In order to build a licensed library into a package, the library must be fully activated on the build computer. With VIPM Professional edition, you can license an unlicensed library at build time. For more information on the professional edition features, please see the VIPM Documentation.
Licensing with VIPM Free Edition
Note: If you get error 1507 during build, it means that the add-on was in an evaluation or invalid state on the build computer. To resolve this, you must first activate the add-on in LabVIEW before building your package.
Licensing with VIPM Pro Edition
With VIPM Pro Edition, you can skip the NI Licensing Tool and use Package Builder to do the library binding: This method is more convenient because it allows you to preserve your original unlicensed source code.
Note: Must be of the form http://solo-instalation-server/ …/unlock/
If you created a license using the free TPLAT Standard mode and the NI-hosted SOLO Server, this URL will be https://softwarekey.ni.com/solo/unlock/
This concludes the Tools Network Developer Center series on VI Package Manager. Click here to return to the Table of Contents to view other tutorials or for more resources for distributing add-ons.