Set Working Folder Does Not "Stick"

[michaelk399]

When I set the working folder for the root folder of my project, I select the option labeled, "Force all subfolders to use inherited working folder." Then I select some of the subfolders. For a while, it appears that everything is OK. Then for no apparent reason, I see the status on all of the files in the subfolder change to "Missing". I presume that is because the system is reverting to the previous working folder, which no longer exists. I go back to the root folder and set the working folder once again. And once again, it appears that the contents of the subfolders are correct - until they go missing again. I am using the Source Gear Vault Client version 4.1.4. Could you please tell me how to set the working folder permanently? Thank you for your time and attention.

[Beth]

Before assuming, click on the folder that holds the files that show as missing. Then look in the upper right corner of your Vault window. What do you see for a working folder?

Are you using Visual Studio integrated with Vault as well as using the Vault client?

[michaelk399]

Dear Beth:

Thank you for responding to my inquiry. Yes, I am using Visual Studio 2005 integrated with Source Gear. Let's say that I select a folder in the vault such as $/Prod/Apps/AppX. What I see displayed in the upper right corner is:

Working folder: C:\Users\michaelk\Projects\Prod\Apps\AppY\AppX

AppX and AppY are two different applications stored in their respective subfolders of $/Prod/Apps. I have no idea how the working folder got that way. I select $/Prod and set the working folder to C:\Users\michaelk\Projects\Prod and select, "Force all subfolders to use inherited working folder," and click on OK. I select $/Prod/Apps/AppX, once again. Now the display in the upper right corner reads:

Working folder: C:\Users\michaelk\Projects\Prod\Apps\AppX

This is the correct working folder. I no longer see the status of "Missing" next to the file names. This setting will last for a while, and then inexplicably reverts back to what you see above. Yes, I am working with Visual Studio at the time. It might help you to know that a couple of weeks ago we had to restore the Source Gear database from backup, and I had to clear out my local cache. I followed the instructions on the Source Gear support forum. Thank you once again for your kind assistance.

[Beth]

Are any projects or files shared across solutions?

[michaelk399]

Yes, many projects are shared across the solutions. I have not been able to find any correlation between the particular project or solution I am working on and the apparent change in the working folder in the Vault client.

[Beth]

Given your situation, it sounds like it's possible that you are getting a conflict between some binding information in Visual Studio and what you have set in Vault. VS can change the working folder for Vault, but the Vault GUI client can't do the same back to the VS bindings.

Since you have projects shared across solutions, you may need to manually bind to get the correct bindings. VS prefers to set the working folder to the common parent, and you won't want that in this case.

Here's what you can do:

• 1) Set the working folder in Vault.
  2) Open the .sln file of the solution on disk. It may give you errors. If it gives an option to permanently remove bindings, do that.
  3) Check the properties of each project to make sure it is referring to the correct disk location.
  4) Go to File - Vault Source Control - Change Vault Bindings.
  5) If everything is bound, unbind it and click OK. If it's not bound, then start with one line that represents a project, select that line and click Bind. You will be asked to select the Vault folder that holds the project. Bind the .sln file last. When finished and all have a status of Valid, click OK.
  6) Check in any changes made to the .sln and .proj files (or .csproj, .vbproj, etc.).
  7) After this, you will no longer use Open from Vault, but instead, just open the .sln from disk or use the Recent Projects link.

If you have an problems getting your project bound to the right location or if it looks like the working folder changed again, send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread. I can walk you through this or see if there's something else going on that I missed.