Have a look to this brand new toolkit for LabVIEW if you are interested to distribute LabVIEW executable with advanced licensing, automatic update capabilities and a lot more amazing features. BLT for LabVIEW (Building, Licensing and Tracking) http://sine.ni.com/nips/cds/view/p/lang/en/nid/211731 BLT for LabVIEW is a stand-alone program you can use to distribute LabVIEW applications for commercial use in a few clicks. License your own LabVIEW application in a few clicks - no coding required Automatically (and remotely) update your applications when you make changes in your LabVIEW code Automate the build process for your LabVIEW executables Get user activity reports and error logs so you can remotely debug your program Use BLT scripting to remotely execute actions on a deployed computer, e.g., update LabVIEW RT Engine Disable parts of your code with features definitions
I am wondering aboout what type of license to use. LGPL or BSD (or maybe some other). I have read through some old discussions here, but since they are 4-5 years old, maybe something has changed. BSD is recommended here, but it is not entirely clear why LGPL is not recommended.
I am looking for someone who wants to sell their license for Application Builder 7.1. Call (919) 807-1752 or email firstname.lastname@example.org.
I am a small-time application builder on Labview, I have tried to find answers to the following two questions a lot on the NI site but could not get any definite yes or no answer
So here are the questions
1) I know that DSC module requires run-time license on the end-users computer, my question is, that if I use the datasocket binding on the controls/indicators property box and assign a couple of OPC tags (like 20-30 max) and not use the shared variable engine, do I still have to get a dsc runtime license, or is there anything like OPC tag-based license for the end-users PC?
2) Does database connectivity toolset and report generation toolkit also require runtime license on end-user PC's?
I'm curious if anyone has had any luck calling 3rd party .net code from LabVIEW that requires a licenses.licx file to be "embedded" into your executable (or else the 3rd party code will complain that it is not licensed.) Apparently this is a common scheme for people using visual studio.
I have a feeling that I may be out of luck here...