LabVIEW
Program Favor
Solved!
@MattWarnock wrote:
I ended up just using my school's version to do it, thanks for all your input guys.
on another note:
I mistakenly used the phrase product, I'm not selling anything I'm simply making a program that will automate a motorcycle throttle and just needed an .exe file so no one running the program would mess up features of the .vi.
dismount those high horses folks
IMHO, if you're going to be writing apps in the real world, you need to mount the high horse. Or risk the wrath of all parties involved bring the legal hammer down upon you. It's good practice to do so now, so when you do it for real, you will be doing it correctly.
Glad you were able to solve your perceived problem. 😉
@MattWarnock wrote:
... just needed an .exe file so no one running the program would mess up features of the .vi.
That's why VIs can have password protection. No exe needed. Keep it simple! 😄
@MattWarnock wrote:
dismount those high horses folks
Horses... motorcycles... same difference. 😄
Personally, I see nothing wrong with building executables for internal educational use. Maybe the Student edition should be able to build watermarked executables, because building executables is a useful skill. If you want, you could post this as in idea in the ideas exchange. 🙂
@altenbach wrote:
Glad you were able to solve your perceived problem. 😉
@MattWarnock wrote:
... just needed an .exe file so no one running the program would mess up features of the .vi.
That's why VIs can have password protection. No exe needed. Keep it simple! 😄
@MattWarnock wrote:
dismount those high horses folks
Horses... motorcycles... same difference. 😄
Personally, I see nothing wrong with building executables for internal educational use. Maybe the Student edition should be able to build watermarked executables, because building executables is a useful skill. If you want, you could post this as in idea in the ideas exchange. 🙂
I agree completly.
Horses and motorcycles are -way- different. Bikes have a mind of their own sometimes.
Locking out code from modification can be done several ways. One is to password-protect the VI. Another is to separate source code from the compiled VI. Neither one of those requires building an EXE.
Regarding EXE builder on student version... That functionality only comes with Professional and Dev Suite. While it is a powerful tool for distributing code, it's not something required to learn LabVIEW which is the overall intended purpose of the student license.
http://www.ni.com/labview/buy/
A better question from OP would have been "How can I lock my code out from modification with the student version since I can't build an EXE?" There's more than one way to skin a cat. 
