LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

move project to another PC

Large LV project with files and dependencies spread across various drives.

 

How can I move this project to another PC?  Want to open project on new PC without any broken links etc.

 

Have tried various methods without success.

 

Please help.

0 Kudos
Message 1 of 33
(6,834 Views)
You could try Source distribution - http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/build_source_distrib/

CLA CTAChampionI'm attending the GLA Summit!
Subscribe to the Test Automation user group: UK Test Automation Group
0 Kudos
Message 2 of 33
(6,825 Views)

I want all files and all dependencies and non-VI's.

 

I want to click on .lvproj file on another PC and start working without any issues.

0 Kudos
Message 3 of 33
(6,823 Views)

Source code control. Check all files in. Go to other computer. Check out. Done.

Message 4 of 33
(6,811 Views)

What do you means Source Code Control?  Is that a menu item in LV?

0 Kudos
Message 5 of 33
(6,804 Views)

I only want to move the LV Project to another computer.  Surely it's not that difficult and doesn't require me to install 3rd party Source Control software.

 

I would have thought ppl would need to do this all the time (move projects from PC to PC).

 

What is the best method to backup a LV project and all dependencies to say a DVD?

0 Kudos
Message 6 of 33
(6,798 Views)

@battler. wrote:

I only want to move the LV Project to another computer.  Surely it's not that difficult and doesn't require me to install 3rd party Source Control software.

 

I would have thought ppl would need to do this all the time (move projects from PC to PC).

 

What is the best method to backup a LV project and all dependencies to say a DVD?


If you are working with large projects you should be using source code control. How do you keep backups, track changes to your code and maintain different versions? Backing up to another disk or a DVD is not a good way to ensure you don't loose anything. Source code control is simply a good programming practice regarldess of the language used.

 

If you are just playing around and experimenting there is no reason to use source code control. If the code is effectively paying your bills or source of your lively hood you are follish not to use it.



Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
0 Kudos
Message 7 of 33
(6,764 Views)

Thanks for stating the obvious Mark.  Any tips/ideas to get me started or you just wanted to tell me off? 😉

0 Kudos
Message 8 of 33
(6,730 Views)

At our plant, we keep all the files in a single directory for each project. Just copy and rename to make a revision. If we use a user library, we copy it to the project directory. This is much easier to move to another machine, user, zip, etc. Of course, source code control is an answer but takes some setup and people buying into it. Plus we transfer projects to other groups in the company that have their own methods and may not want to use SCC.

0 Kudos
Message 9 of 33
(6,715 Views)

@.:aCe:. wrote:
You could try Source distribution - http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/build_source_distrib/


Go back and read the first answer you got to your question.

 

Or since you did not organize your project file on your hard drive from the start, you can try to copy them manually.

Omar
0 Kudos
Message 10 of 33
(6,708 Views)