km4hr Posted October 17, 2008 Report Share Posted October 17, 2008 Aspiring labview programmer wants to know how to turn a completed VI into an application that can be run by others without leaving it wide open to modification. Is this possible? Is there an "execute-only" mode? km4hr Quote Link to comment
Aristos Queue Posted October 17, 2008 Report Share Posted October 17, 2008 Try this menu item: File>> VI Properties >> Protection >> Password Protected Quote Link to comment
jgcode Posted October 17, 2008 Report Share Posted October 17, 2008 QUOTE (km4hr @ Oct 16 2008, 11:44 AM) Aspiring labview programmer wants to know how to turn a completed VI into an application that can be run by others without leaving it wide open to modification. Is this possible? Is there an "execute-only" mode?km4hr If you turn the VI's into an application (e.g. build an executable) they :ninja: won't be able to get at the code. Quote Link to comment
km4hr Posted October 17, 2008 Author Report Share Posted October 17, 2008 QUOTE (jgcode @ Oct 16 2008, 05:32 AM) If you turn the VI's into an application (e.g. build an executable) they :ninja: won't be able to get at the code. How is this done? Where do I go to find out? I looked around a bit and the best I can tell this requires optional (ie expensive) software. Is that correct? thanks QUOTE (Aristos Queue @ Oct 15 2008, 10:56 PM) Try this menu item: File>> VI Properties >> Protection >> Password Protected Excellent! Thank you. Quote Link to comment
Francois Normandin Posted October 17, 2008 Report Share Posted October 17, 2008 QUOTE (km4hr @ Oct 16 2008, 08:26 AM) How is this done? Where do I go to find out?I looked around a bit and the best I can tell this requires optional (ie expensive) software. Is that correct? You need the Application Builder. Quote Link to comment
jgcode Posted October 17, 2008 Report Share Posted October 17, 2008 QUOTE (km4hr @ Oct 16 2008, 09:26 PM) How is this done? Where do I go to find out?I looked around a bit and the best I can tell this requires optional (ie expensive) software. Is that correct? The application builder is included in the professional version and dev suite otherwise it is an add-on. Log onto ni.com for prices in your area. Quote Link to comment
km4hr Posted October 17, 2008 Author Report Share Posted October 17, 2008 QUOTE (jgcode @ Oct 16 2008, 09:40 AM) The application builder is included in the professional version and dev suite otherwise it is an add-on.Log onto ni.com for prices in your area. I work for a university so perhaps I have it already. How would I know? I'll check with our license coordinator. Thank you all for helping this newbie (1 week experience) with what may seem like trivial questions. I hope to get beyond the struggling stage shortly. thanks Quote Link to comment
gmart Posted October 17, 2008 Report Share Posted October 17, 2008 QUOTE (km4hr @ Oct 16 2008, 11:19 AM) I work for a university so perhaps I have it already. How would I know? I'll check with our license coordinator.Thank you all for helping this newbie (1 week experience) with what may seem like trivial questions. I hope to get beyond the struggling stage shortly. thanks You can create a new LabVIEW project (File>>New Project...) which will have a Build Specification node. When you right-click on it, you will see a list of build types you can create. If the application builder is present/licensed, you will see an option - Application. You can get more help regarding build specifications by selecting Help in the right-click menu. Quote Link to comment
PaulG. Posted October 18, 2008 Report Share Posted October 18, 2008 QUOTE (km4hr @ Oct 15 2008, 10:44 PM) Aspiring labview programmer wants to know how to turn a completed VI into an application that can be run by others without leaving it wide open to modification. Is this possible? Is there an "execute-only" mode?km4hr ForCryinOutLoud! WTH are we doing here, guys? It's LabVIEW, not "labview". And if KM4HR wants to "protect" precious intellectual property ... ... just tell him/her to save their code onto their own personal thumbdrive. What are we doing here?? And why do I keep coming here?? Quote Link to comment
jgcode Posted October 18, 2008 Report Share Posted October 18, 2008 QUOTE (PaulG. @ Oct 17 2008, 10:23 AM) ForCryinOutLoud! WTH are we doing here, guys? It's LabVIEW, not "labview". And if KM4HR wants to "protect" precious intellectual property ... ... just tell him/her to save their code onto their own personal thumbdrive.What are we doing here?? And why do I keep coming here?? Now that's one way to stop the growth and decrease the reputation of an open forum such as LAVA: Telling people they aren't good enough to be given a correct answer to a legitimate question, even after that person explicitly said they are a newbie and have thanked previous posters for their constructive comments. Way to go! <edit> I actually do not have a problem with people having an opinion like the above - as everyone is entitled to one. I just see how it was helpful to the issue at hand (or the community as a whole) in any way, shape or form, to actually go ahead and post it. </edit> Quote Link to comment
km4hr Posted October 18, 2008 Author Report Share Posted October 18, 2008 QUOTE (PaulG. @ Oct 16 2008, 09:23 PM) ForCryinOutLoud! WTH are we doing here, guys? It's LabVIEW, not "labview". And if KM4HR wants to "protect" precious intellectual property ... ... just tell him/her to save their code onto their own personal thumbdrive.What are we doing here?? And why do I keep coming here?? IP security is not my goal. I'm building a LabVIEW application that will be used by students at the university where I work as undergraduate lab manager. The students will take apart (ie break) any LabVIEW application I create if it's easy to do so. I just want to reduce the chaos by making it a little harder for students to modify my work. jgcode, Thanks for your support. I've used enough forums to realize that there will always be a few paulg's around. It's no big deal. The vast majority of LAVA posters are very generous with their knowledge. thanks again, km4hr QUOTE (jgcode @ Oct 17 2008, 01:36 AM) Now that's one way to stop the growth and decrease the reputation of an open forum such as LAVA: Telling people they aren't good enough to be given a correct answer to a legitimate question, even after that person explicitly said they are a newbie and have thanked previous posters for their constructive comments. Way to go! <edit> I actually do not have a problem with people having an opinion like the above - as everyone is entitled to one. I just see how it was helpful to the issue at hand (or the community as a whole) in any way, shape or form, to actually go ahead and post it. </edit> Quote Link to comment
TobyD Posted October 18, 2008 Report Share Posted October 18, 2008 QUOTE (PaulG. @ Oct 16 2008, 06:23 PM) ForCryinOutLoud! WTH are we doing here, guys? It's LabVIEW, not "labview". And if KM4HR wants to "protect" precious intellectual property ... ... just tell him/her to save their code onto their own personal thumbdrive. I couldn't help but point out that it's km4hr not "KM4HR". I hope today is going better for you PaulG. Quote Link to comment
Francois Normandin Posted October 18, 2008 Report Share Posted October 18, 2008 QUOTE (km4hr @ Oct 17 2008, 10:22 AM) The students will take apart (ie break) any LabVIEW application I create if it's easy to do so. I just want to reduce the chaos by making it a little harder for students to modify my work. Ah... I can tell you that researchers will do the same thing, not only students! I'd keep a copy of the original code in a Code Repository on a separate disk, and use passwords to protect the diagram from tempering. Quote Link to comment
PaulG. Posted October 19, 2008 Report Share Posted October 19, 2008 QUOTE (km4hr @ Oct 17 2008, 10:22 AM) IP security is not my goal. I'm building a LabVIEW application that will be used by students at the university where I work as undergraduate lab manager. The students will take apart (ie break) any LabVIEW application I create if it's easy to do so. I just want to reduce the chaos by making it a little harder for students to modify my work. jgcode, Thanks for your support. I've used enough forums to realize that there will always be a few paulg's around. It's no big deal. The vast majority of LAVA posters are very generous with their knowledge. thanks again, km4hr I screwed up. Big time. I won't apologize for what I said, but all of you could have done without my sarcasm and the ugly way I said it. I was tired and grumpy, but that is no excuse for the lack of respect I showed all of you, especially you, km4hr. For that I sincerely apologize for the way I said it and ask for yours and everyone else's forgiveness. What I meant to say: Password-locked LV code is real pet peeve of mine. Unless you intend to sell your source code as "intellectual property" passwords are almost always a very bad idea. The code you lock with a password invariably is the code someone else will inherit and maintain. Years ago I inherited a huge application where numerous, critical sub-VI's were password-protected. Just a few weeks ago I wanted to look at that code in my archives to help me with an issue I was dealing with at the time. Lo and behold I had forgotten the password. If you are concerned with someone messing around with your code you have far more serious issues in your working environment and a password would be nothing more than a Band-Aid. Regarding a thumb drive: everything I do I save to my thumb drive at the end of every single day. Its main purpose is to take my work home, but also, if someone changes my code I always have my version ready to replace it. Quote Link to comment
crelf Posted October 19, 2008 Report Share Posted October 19, 2008 QUOTE (PaulG. @ Oct 18 2008, 02:26 PM) Unless you intend to sell your source code as "intellectual property" passwords are almost always a very bad idea. The code you lock with a password invariably is the code someone else will inherit and maintain. Years ago I inherited a huge application... Passwording the code that you use while developing just doesn't make any sense, for the reasons PaulG mentions. Keep it safe in SCC that has security implemented by yout IT department - they're the experts, and have probably thought of IT security a lot more than you have. Don't try to handle it yourself at the VI block diagram level - you're only settingn yourself up for a lot of hurt. That said, password protecting the code that you distribute to protect your IP can be sensible (as long as you understand the risks and limitations of doing so). QUOTE (PaulG. @ Oct 18 2008, 02:26 PM) ...everything I do I save to my thumb drive at the end of every single day. Its main purpose is to take my work home, but also, if someone changes my code I always have my version ready to replace it. My suggestion is in two parts: get a laptop (if you can), and http://thinkinging.com/2007/06/17/top-5-bad-excuses-for-not-using-source-code-control/' rel='nofollow' target="_blank">use SCC. Conbine the two into your normal operating proceedure, and you won't even have to think about it. Quote Link to comment
PaulG. Posted October 21, 2008 Report Share Posted October 21, 2008 QUOTE (crelf @ Oct 18 2008, 03:08 PM) That said, password protecting the code that you distribute to protect your IP can be sensible (as long as you http://thinkinging.com/2007/08/19/password-protecting-vis-is-security-through-obscurity/' rel='nofollow' target="_blank">understand the risks and limitations of doing so). Thanks mate. :thumbup: Quote Link to comment
crelf Posted October 21, 2008 Report Share Posted October 21, 2008 QUOTE (PaulG. @ Oct 19 2008, 08:09 PM) Thanks mate. :thumbup: No worries cobber! Quote Link to comment
jcarmody Posted October 21, 2008 Report Share Posted October 21, 2008 QUOTE (crelf @ Oct 18 2008, 03:08 PM) , and http://thinkinging.com/2007/06/17/top-5-bad-excuses-for-not-using-source-code-control/' rel='nofollow' target="_blank">use SCC. I'm on a team of developers that doesn't use SCC, but I use Tortoise SVN for my work. My question is not how this will benefit me, but whether my experience with it will help when I sit for the CLA exam (someday, perhaps next year, not sure when, not nearly ready...). The stuff I read from NI mentions $oftware that I don't have. Thanks, Jim Quote Link to comment
crelf Posted October 21, 2008 Report Share Posted October 21, 2008 QUOTE (jcarmody @ Oct 20 2008, 06:09 AM) I'm on a team of developers that doesn't use SCC... Is there an excuse for not using SCC? You're on a team - do you share any code? How do they control versioning, rollback to previous versions, etc? Make the, at the very least, read this. QUOTE (jcarmody @ Oct 20 2008, 06:09 AM) My question is not how this will benefit me, but whether my experience with it will help when I sit for the CLA exam Yes - having SCC exoerience will help you with the CLA. Quote Link to comment
Dan DeFriese Posted October 21, 2008 Report Share Posted October 21, 2008 QUOTE (jcarmody @ Oct 20 2008, 05:09 AM) The stuff I read from NI mentions $oftware that I don't have. I believe Perforce (the tool NI claims to use internally) is free for 1-2 seats used non-commercially. I have yet to take the CLA (I'm taking the CLD on the 31st), but I'd be surprised if the test required in-depth knowledge of a specific SCC tool. Quote Link to comment
TobyD Posted October 21, 2008 Report Share Posted October 21, 2008 QUOTE (PaulG. @ Oct 18 2008, 11:26 AM) I sincerely apologize...Regarding a thumb drive... I figured you must just be having a bad day because your reply seemed a bit out of character. :thumbup: As for the thumb drive - I strongly recommend that you not rely on this as the only form of backup you employ. Others have mentioned SCC, which is ideal, but even if you think that is overkill don't rely on just a thumb drive. I have seen those things corrupt data so many times I would never rely on them as my backup plan. Quote Link to comment
jcarmody Posted October 21, 2008 Report Share Posted October 21, 2008 QUOTE (crelf @ Oct 20 2008, 09:53 AM) Is there an excuse for not using SCC? No... But, I use it! There are only two of us using LabVIEW; the other guy uses LabWindows. QUOTE You're on a team - do you share any code? Not really... I've used VIPM to package some of my own reusable bits, but haven't shared them. QUOTE How do they control versioning, rollback to previous versions, etc? These aren't fun questions QUOTE Yes - having SCC exoerience will help you with the CLA. Even if it's only with Subversion? I recognize the need for this, among other things; I started http://forums.lavag.org/requirements-document-t12141.html&p=52947#entry52947' target="_blank">another thread about requirements documents last week. Thing is, I've got a long way to go before I can lead an effort to change these things, but I'm reading/trying/learning to position myself to improve myself first, then I can be better able to affect the team. Quote Link to comment
crelf Posted October 21, 2008 Report Share Posted October 21, 2008 QUOTE (jcarmody @ Oct 20 2008, 01:15 PM) Even if it's only with Subversion? The implementation of the specific SCC utility that use isn't important - the theory behind SCC is. Quote Link to comment
km4hr Posted October 22, 2008 Author Report Share Posted October 22, 2008 QUOTE (PaulG. @ Oct 18 2008, 02:26 PM) I screwed up. Big time. I won't apologize for what I said, but all of you could have done without my sarcasm and the ugly way I said it. I was tired and grumpy, but that is no excuse for the lack of respect I showed all of you, especially you, km4hr. For that I sincerely apologize for the way I said it and ask for yours and everyone else's forgiveness.What I meant to say: Password-locked LV code is real pet peeve of mine. Unless you intend to sell your source code as "intellectual property" passwords are almost always a very bad idea. The code you lock with a password invariably is the code someone else will inherit and maintain. Years ago I inherited a huge application where numerous, critical sub-VI's were password-protected. Just a few weeks ago I wanted to look at that code in my archives to help me with an issue I was dealing with at the time. Lo and behold I had forgotten the password. If you are concerned with someone messing around with your code you have far more serious issues in your working environment and a password would be nothing more than a Band-Aid. Regarding a thumb drive: everything I do I save to my thumb drive at the end of every single day. Its main purpose is to take my work home, but also, if someone changes my code I always have my version ready to replace it. Everything is fine, PaulG. Glad you cleared that up. I know the feeling. I said something once that didn't come out right :headbang: Been there, done that. Hear yea, everyone! PaulG is a nice guy that stands firm on his convictions! km4hr Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.