Save Project As option?

[stgislander]

I have a LabVIEW project that I want to use as the baseline for a new project.  LabVIEW 2022 Q3 (32-bit) does not have a Save Project As option.  Not even a "greyed out."

To create this new project, is it just a matter of copying everything into a new project folder and renaming any files that need renamed?

[BertMcMahan]

Technically it's just called "Save As", not "Save Project As", on my version 20 installation-

Did they take that out at some point?

[stgislander]

I have the same pull down menu.

I interpreted that as a "file" Save As, and not a "project" Save As.

I'll look at it again though.

[Kyle97330]

Note that the "save as" option there creates a new ".lvproj" file but nothing else.  It sounds a bit like you want to create a copy of every file, not just the ".lvproj" file.

If you use some LabVIEW code you can create copies of everything in your project.  Here's code I created to copy one of my projects:

This was for a particular project where I only wanted to copy contents of virtual folders 1 deep, plus classes.  It also copied the stuff into a kind of weird folder structure, but it did do the copying of everything.  If this is what you need, you could start there and then move the files it copies if you don't like their new locations.

[stgislander]

Thanks for the code suggestion.  

I tried Save As and yeah, that's not what I was thinking. It copied my original project folder structure into the new folder.  It also made copies NI specific folders from Program Files and Program Files (x86) folders in the new folder I created.  

[BertMcMahan · Accepted solution]

If you select "Save As" then "Duplicate .lvproj file and contents" it will re-create everything in that project, which it sounds like is what you wanted with the exception of the NI stuff. Choose the "Select contents to copy" button and de-select the NI stuff and it'll just make a duplicate of your project, but it will have the names and locations right so you don't wind up with a bunch of warnings that items were found in new locations (which can happen if you just copy/paste the project folder).

[stgislander]

That worked better than my first attempt.  Now I just have a lot of .ctl file conflicts to resolve.

[altenbach]

Another option is to "save for previous" and pick the same version. Make absolutely sure that all relative paths are clean, though, else you get very deep hierarchies.

[stgislander]

I want to thank everyone for the great suggestions.  After cleaning up the conflict resolutions, I've got a "new" project.

[billko]

---

@stgislander wrote:

I want to thank everyone for the great suggestions.  After cleaning up the conflict resolutions, I've got a "new" project.

---

Just curious how you cleaned it up.  Usually I just delete the original so all ties to it are broken.  (I can always recall the original from GIT/SVN.)