Making a copy of a large project

[jvh75021]

Management wants us to make a copy of our TS project for engineering use so that the production code will not be touched. It is fairly large, about 12 sequence files and 1600 VIs. It was built with relative paths for the VIs but I am afraid the project and workspace files will be a mess. But my biggest concern is that the original project will be corrupted for I can't say for certain that the original developer put all files under ClearCase control.

Surely others have copied large projects. Any suggestions on how to proceed or not.

Thanks,

jvh

[RayFarmer]

Hi,

It shouldn't be a problem providing you have use relative paths for the SequenceCalls as well. But if you have used a management tool such as ClearCase then you are always going to beable to get back to the original code.

[jvh75021]

I should be able to get back to original but funny things happen. I copied topLevelDir to TBandTopLeveDir and prefixed the original with an x so labView wouldnt find it.I opened a VI in the new dir, edited it, and closed TS and LV.. When I opened the same VI in the original directory I got a pageful of dependency messages. Seems like LV is keeping it's own dependency info somewhere. I also run into this kind of problem when I open a VI from an archive directory. If the same name appears in my current directory I am going to have problems.

[RayFarmer]

Yes that always been a big problem with LabVIEW but I thought things had improved when using LabVIEW projects. TestStand 2010 also using the LabVIEW projects as well.

If using pre-project based LabVIEW then use the save as and make a copy that way as all subVI will be correctly relinked to the new directory.