Regarding Access Rights to Build Specification in Project Explorer

[nspl]

I m using LV2016. I want to apply some restriction to Build Specification function in project explorer like I don't want to allow all user to build any Exe/Installer/Source Distribution. Only users with access can use this functions. Is there any way?

[rolfk]

No! If you are allowed to open a project you are also allowed to make changes to it, run any target specification and all else.

You could post to the LabVIEW Idea Exchange, but my guesstimate for the probability to add such a feature to the LabVIEW project is somewhere around LabVIEW 2500.

[RTSLVU]

---

@nspl wrote:

I m using LV2016. I want to apply some restriction to Build Specification function in project explorer like I don't want to allow all user to build any Exe/Installer/Source Distribution. Only users with access can use this functions. Is there any way?

---

This is a very odd question, and I cannot think of a reason why you would give someone full access to the development environment but not to compiling programs.

But back in the day the compiler (Application Builder) used to be a separate purchase, so it might be possible for "deactivate" the Application Builder. But you might need to buy a license that does NOT come with it, as someone could simply use the same serial number to reactivate it.

I believe the Application and Installer Builders are actually an extra add-on for the LabVIEW "Base" and "Full" editions.

[nspl]

Yes, i know this is a very odd question. I don't want everyone to use modules I have developed and build applications from it. That's why i want to apply restriction to build specification like no one can build any applications without access in our organisation.

[rolfk]

The closest thing that you have is the Third Party Licensing Toolkit. That allows you to make a few selections about how a library can be used and if someone is allowed to view the diagram of the VIs inside the library.

It basically gives you control over who can run your VIs (only those you issued a license to) and optionally if the diagram is visible without a license or not.

But, the licensing happens over the NI server (unless you buy your own Software Key Solo server license and run it yourself) and NI wants a cut on your license fees for running the servers.

Also if you are employed you should check with your lawyer. Trying to encumber software you created for your employer can certainly get you fired and worse. And if your employer requires such a restriction it is their task to check out the options and decide how to go about it. They do not want to end up being locked out of software that they paid you to create.

[JensG69]

I agree with Rolf, TPLAT could be a solution for your question.

cf. here for further reading.

TPLAT standard mode is free for LabVIEW customers, so this would give you an option to license a library, so that users without a validy licensed library cannot create executables.

However such a licensed library is not bound to a username but the machine/system it is installed on. In addition after the end to the 30 day trail period you cannot run any source-code that make use of your modules.

Regards, Jens

[nspl]

Thank you Everyone for your ideas. I will try with Third Party Licencing and Activation Toolkit.