Project move option in version 6 of CVI

[rdoan]

After upgrading to Version 6 of CVI, I have problems moving the project to a different drive or directory.

[davidx]

Check if you selected the correct directories in:
Build->Target Settings...

[rdoan]

I have the correct Build->Target Settings. There used to a menu Options->Project Move Options that would fixup the path names in the project file list. I can't find it now.

[Ted F.]

The link to "Options->Project Move Options" that was available in earlier versions of CVI is no longer available in the same sense for CVI 6.0. But there are other ways to fix the path names in the project file list. Since the project file is basically just a text file, you're able to open it in a text editor and manually change it. When you open it, just modify the paths for the project and included files.

[aperez]

Hi Rdoan,

What kind of problems are you encountering when moving your project to a different directory? I'm curious because we didn't really change the functionality behind the Project Move Option that used to be in earlier versions of CVI. We still "fix up" paths for you whenever possible; although this is done behind the scenes. However in some cases the project might not be able to locate a file if its path has changed and it cannot find it in its subdirectories.

Please let me know how we can help.

Azucena Perez
CVI

[rdoan]

Now I understand. It is fixing up the paths where the tree was the same. Only not where the tree has changed. Thanks for your response!

[vkaski]

It is not fixing up paths , if project is moved into different network drive letter.
In CVI 5.5 it was doing it and I'm really missing that feature. Will there be any fix ?

[TerriW]

I agree. I am also having problems with the project moves not fixing the paths in CVI 6.0. Has there been an adequate response to this problem yet or an indication of when/if a fix will occur?

[mark232]

Out of curiousity, has any comments been made concerning this thread?

Thanks,
Mark

[aperez]

For the record, this is how CVI 6.0 fixes up paths of moved files:
If the project is moved to a different letter drive, and if files contained in the project are not under the project's folder (or subfolders), then CVI 6.0 will not be able to "fix up" the file paths. For example if I have project1.prj under the following directory structure:

c:\temp\myproject\project1.prj
c:\temp\myproject\main.c
c:\temp\myproject\main.h
c:\temp\myproject\main.uir

then when I move project1.prj (and its files) to:

d:\temp\myproject\project1.prj
d:\temp\myproject\main.c
d:\temp\myproject\main.h
d:\temp\myproject\main.uir

CVI will be able to resolve the new paths because the files are at the project level. However if the files were located in an unrelated directory, a
s such:

c:\temp\myproject\project1.prj
c:\anotherfolder\main.c
c:\anotherfolder\main.h
c:\anotherfolder\main.uir

then when you move project1.prj (and its files) to another directory, CVI might not be able to fix the paths of the files under "anotherfolder". This is directly related to how CVI stores filepaths. There are two choices, relative vs. absolute path. Relative paths are easy to fix since they are relative to the project file. Absoluate paths are not "fixable" and cannot be changed.

By the way, the next version of CVI will be able to find files anywhere, even across driver letters, regardless of their location relative to the project file! If you are interested in checking out the next CVI (beta), go to ni.com/beta

Regards,
Azucena