Protection of source distribution

[andrej]

Hi,

I have created an application with plugin architecture (Labview classes). When I distribute these plugins all VI are unprotected. I know that I can password protect VIs, but is this save way for protecting against stealing source code?

What are other options for protection? Something like DLL would be great, but I can not use it because plugins have user interfaces.

Can removal of front panel and block diagram be of any help here?

Thanks!

[smercurio_fc]

This question has been asked before numerous times, with various suggestions given. Have you tried a search? Certainly stripping the block diagram is a viable option. NI also provide a licensing toolkit which may work for you. Please search the forum and see what's already been suggested. If you want to discuss the pros and cons of a specific approach, post back.

[Dennis_Knutson]

And exactly why do you think you cannot create a dll? Your statement about front panels seems to indicate that you think a dll cannot have a front panel. That is, of course, wrong.

[andrej]

Dennis, yes I was wrong about dll having front panel.

smercurio_fc, I have searched forum regarding the question, but I would like to know if striping the block diagram and/or front panel is safe option for distribution of plugins. I do not want that someone can use plugins that come with the main application for it own purpose.

[Dennis_Knutson]

Personally, I think removing the block diagram is wrong since it prevents the user from user the VIs with a newer version of LabVIEW. Whether you password protect the VIs or remove the block diagram, that still would not prevent someone from calling the VIs from a different VI. If you feel like you really need to do this, you would need the licensing toolkit.

I'm not at all sure why it would be such a big deal if someone were to use a VI that they have purchased in any way they saw fit.

[smercurio_fc]

---

andrej wrote:

smercurio_fc, I have searched forum regarding the question, but I would like to know if striping the block diagram and/or front panel is safe option for distribution of plugins. I do not want that someone can use plugins that come with the main application for it own purpose.

---

Well, if you strip out the block diagram they certainly can't copy the code. As for using them for their own purpose, you'll need to be a bit more specific as to what you mean by that. If the VIs have adequate documentation as to what they do, and/or their use is obvious, there's nothing that would stop someone from using that VI for something else (even with the block diagram stripped out).

[JÞB]

The only idea I can come up with to limit the scope of use of any vi you supply would be to add an authentication key (case structure) around every vi probably tied to a functional global writen only by the "owning ancestor" then rip out the BD's.

Of coares, I might not buy a program from you again if you took the time to do all that.