Search the Community
Showing results for tags 'license'.
Found 5 results
-
Dear LabVIEW Developer, We are really pleased to introduce today our new toolkit: BLT for LabVIEW. We worked hard to provide a powerful management software that will give you the tools to protect and distribute your LabVIEW programs, for internal or commercial use. As a LabVIEW developer, your feedback is really important to us since our toolkit is mainly designed for your needs. That's why we would like to offer you a free version with all the features included, so you can test BLT and see how it improves your daily productivity. Please refer to www.BLTforLabVIEW.com (http://bltforlabview.com) or watch the video for more information. http://youtu.be/WfYCWNRtar8 We really appreciate your collaboration, and hope that you will find a lot of value in this new LabVIEW Toolkit. Matthias Baudot Principal Software Architect STUDIO BODs INC. contact@studiobods.com -
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. Thanks
-
I am looking for someone who wants to sell their license for Application Builder 7.1. Call (919) 807-1752 or email george.mundy@skilledengineer.com. -George -
Hello Everyone, 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...
