move project to another PC

[deyyoung]

My 2 cents:

Option 1) From the Project Explorer window, click File->Save As ..., then select "Duplicate .lvproj file and contents".  Click on the help button to read more about how the two options work ("Include All Dependencies" vs. "Select contents to copy").  I've never done this, and you may have already tried it, but it seemed like the most likely method.

Option 2) Manual copy.  In the Project Explorer window, Click Project->File Information.  This will show where all your files are located.  Click Export File Paths... to get a text file list of all the paths.  Then, manually copy these over into a single directory structure.  You will have to re-link everything, but afterwards you can copy it over to another PC at least; plus, it's a good way to force a re-organization of your project. 

[See - I forced myself not to preach source code control to you ... your welcome! 🙂 ]

[Ben]

Two methods work well for me.

From the project do a save for previous but lie to LV and chose the current version and navigate to where you want to save it.

Second:

Create Source distribution and customize it to preserve teh hiarchy.

The only thing that would be missing is the add-ons for LV that require an install.

No SCC required.

Ben

[Mark_Yedinak]

---

@battler. wrote:

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

---

You can take it as being told off or as good advice given from years of experience. If you are making your living off of this code and these projects you should adopt best practices for your development environment. This includes using source code control. It is fairly easy to install and use SVN even for a single user and computer. You mentioned you are using large projects. Taking short cuts will eventually byte you in the butt. I am not trying to put you down. Just trying to give sound advice which in the long run will make your life easier. Using the above methods to copy the project will work in the short term but you will spend quite a bit of time keeping the two copies in synch with each other. This is exactly what source code control will o for you.

[battler.]

Thanks everybody.

Mark, you must just be the telling off type.   I enjoyed your use of "byte you in the butt".   Point made and taken.

[smercurio_fc]

---

@battler. wrote:

Thanks everybody.

Mark, you must just be the telling off type.   

---

No, that would be me.

[Mark_Yedinak]

---

@battler. wrote:

Thanks everybody.

Mark, you must just be the telling off type.  

---

Not really. Just a strong advocate of doing things right.

(It's tough at times to come across the right way using a keyboard.)

[battler.]

---

@Ben wrote:

Create Source distribution and customize it to preserve teh hiarchy.

---

Could you explain this process in a little more detail.  Would you use Tortoise to do this?  What do you mean "customise it to preserve heirarchy"?  How do you preserve heirarchy using source distribution?  Is this the same as source code distribution?

[Mark_Yedinak]

---

@battler. wrote:

---

@Ben wrote:

Create Source distribution and customize it to preserve teh hiarchy.

---

Could you explain this process in a little more detail.  Would you use Tortoise to do this?  What do you mean "customise it to preserve heirarchy"?  How do you preserve heirarchy using source distribution?  Is this the same as source code distribution?

---

This is an option in the LabVIEW project. It is one of the build options.

[Ben]

---

@Mark Yedinak wrote:

---

@battler. wrote:

---

@Ben wrote:

Create Source distribution and customize it to preserve teh hiarchy.

---

Could you explain this process in a little more detail.  Would you use Tortoise to do this?  What do you mean "customise it to preserve heirarchy"?  How do you preserve heirarchy using source distribution?  Is this the same as source code distribution?

---

This is an option in the LabVIEW project. It is one of the build options.

---

[Ben]

RE: SCC ...

---

@Mark Yedinak wrote:

---

@battler. wrote:

Thanks everybody.

Mark, you must just be the telling off type.  

---

Not really. Just a strong advocate of doing things right.

(It's tough at times to come across the right way using a keyboard.)

---

In the interest of questioning all accepted standards I have to question...

So before SCC was invented we backed stuff up and kept track of our development forks just fine. There was no need for "nanny-code" forcing us to check stuff out and in etc (oops did I just reveal my heart re SCC?).

Was I doing thing WRONG bak then?

If I dislike SCC and get by fine without it, am I wrong now?

In the big picture I don't care for SCC being pushed as the only way to do it "right". It like football helmets just encorage people to take risks they would not take if they did not have SCC doing the data-police thing.

My beef is not with doing backups (meganointo may it not be so) but with this popular ... fable that "SCC or you are wrong".

So, is the emporor realy naked?

Ben