Is it possible to build exe with vis that have striped block diagrams?

[Thomas_robertson]

For real?  So anybody making an exe in LV 2010 and selling is opening the door for anyone else to extract the vi's compile them into their code and sell a competing product?  

Do you have a link to the method and hopefully some way of preventing it?

[F._Schubert]

Start here:

http://thinkinging.com/

There is an older blog post that describes the situation in LV7/6.

Edit: there are some OpenG tools to make it more difficult like 'mangle names' and using the OpenG builder to automate this. Described in the blog mentioned above.

Felix

[Jervin Justin]

You could try the Third-Party Licensing & Activation Toolkit to protect your VIs.

This is a free toolkit we released this year to add licensing to LabVIEW code which enables LabVIEW devolopers to protect their IP while at the same time making it easy to create evaluation versions of their software.

[Ben]

---

@f. Schubert wrote:

Start here:

http://thinkinging.com/

There is an older blog post that describes the situation in LV7/6.

Edit: there are some OpenG tools to make it more difficult like 'mangle names' and using the OpenG builder to automate this. Described in the blog mentioned above.

Felix

---

THere was also a discusion on LAVA about "in-lining" code. This referes to what amounts to a pre-compiler (yes I know that term is a strech) that replaces all sub-VIs with the evielent code. THe idea is that hackers can't use your sub-VIs because.... there are no sub-VIs.

Ben