LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Adding a copy of an existing VI to project

Solved!
Go to solution

Greetings everyone. This should be very simple but for some reason it is driving me crazy. I will admit it has been a while since I have done anything in labview so my apologies for asking what some may consider a dumb question lol.

 

I inherited a labview 2017 project that was written by an outside contractor a little over 5 years ago. Some changes have been requested to the program while at the same time retaining the original. The project is complete with the build files for the executable. I have already duplicated the build and renamed it. All I need to do is copy the main VI, rename it, and add it to the project. At that point I can load it and make the necessary changes. I would then go into the build that I copied and renamed and change the main VI to the modified one.

 

Again, it should be super simple but for some reason it is making me crazy. Could someone please provide a step-by-step procedure to do what I asked?

 

Copy existing VI in a project

Rename it

Add the new file into the project

 

That's about it. Thanks!

0 Kudos
Message 1 of 4
(1,808 Views)
Solution
Accepted by topic author Dragonrider
  1. Open the VI you want to duplicate.
  2. File >> Save as.
  3. Select Open additional copy. Enable Add Copy to .lvproj or lvlib

ZYOng_0-1697582273648.png

 

-------------------------------------------------------
Control Lead | Intelline Inc
0 Kudos
Message 2 of 4
(1,795 Views)

Thank you! Exactly what I was looking for. All set now

0 Kudos
Message 3 of 4
(1,695 Views)

Of course the way to deal with this is to put the project in source code control, so you can go back and forth freely. You don't have to (and really shouldn't) copy at all.

 

How are you going to develop your copy when subVIs (hoping there are subVIs) start changing? Copy those too? It will get old fast.

 

"Duplicate" usually isn't a good idea in software production.

 

Just a friendly warning...

Message 4 of 4
(1,678 Views)