Project Relocation results in invalid file paths

When one relocates the target of a wyBuild project from one folder or drive to another (moved my VS Project folder to new location) all the references in the .wyp project file are invalid and show red. This is good error checking, but without manually reselecting each file and mapping the new path for each version, is it possible to change the files in bulk? My project has some 438 references to update which is why I was wondering if there were a quicker way.

I was wondering if there were a quicker way.

Unfortunately, no. We plan on switching from "full path" storage to "relative path" storage, but it's still a couple of weeks away.

I hate for you to have to change every one of the references by hand, but unfortunately this isn't a 1 or 2 day fix.

Is it possible to postpone moving the files until after we've fixed this?

No worries. I'll take care of it. I think if I just duplicate the release version, drag and drop the files from the new location it will correct itself. I just have to remember that if I rebuild those releases it'll use the latest code from the project directory. Otherwise I'd have to role back in source control first. I assume that the existing .wyu files won't be overwritten if I do this.

I don't think I quite understand you. If you move all of the files from every version, then you have to re-add all of the files from every old version. If you only add the latest version you will lose the ability to make patch files from old versions to the latest version.

I assume that the existing .wyu files won't be overwritten if I do this.

Your update output folder is, by default, relative to wherever the project file is. You can change this in File > Properties > Update & server files.

I understand what you are saying. I moved all of my User directories to a new drive due to disk space issues and your are correct, I'll have to manually remap them all for each version.