Search the Community
Showing results for tags 'license'.
Found 6 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://bltforlabvi -
Copyright, trademarks - all this legal stuff gets tricky! Here is a documented experience from a LabVIEW development company that had to change their brand names due to a conflict. Licenses can get complicated too. Did you know that any application you create in LabVIEW requires a copyright notice regarding NI? Essentially I want to make it easier for users and to lessen confusion (if any) when using OpenG. So, I want to start by talking about the OpenG licenses. There has been some questions raised about how to license applications that make use of OpenG libraries (e.g. here). See here for
-
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?
-
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...
