Visual Studio 2005 beta clears the working folder

[jmarsch]

When using Vault 3.0.x with Visual Studio 2005, I notice that the working folder settings in Vault keep getting cleared and reset. Is this a bug?

[lbauer]

Possibly. We haven't fully tested Vault 3.0.x with VS 2005.

VS 2005 is fully supported with the release of Vault 3.1. I'd suggest you upgrade at least your clients Vault 3.1.1, the latest release. And I'd recommend upgrading the server as well. For best results, client and server versions should match.

Then if you continue to experience difficulty, post the details and we'll try to determine the problem.

[dan]

Visual Studio controls this by telling us to unset and set the working folder.

Does the working folder keep changing? If not, how can you tell it keeps getting cleared and reset?

[kadorken]

Similar problem, but VS2005 CHANGES working directory Keith Dorken, 2005-08-19

I am experimenting running VS2003 and VS2005 on the same machine, with VAULT. I set the working directory for VS2003 to C:\MSNET I open VS2003; my source control bindings are correct (they were bound to C:\MSNET) I close VS2003; I open VAULT and set the working directory to C:\MSNET2005 I GET the latest version from VAULT into C:\MSNET2005 If I open VS2003 at this point, all the source bindings are incorrect in VS2003; I close VS2003 without changing anything. I open VS2005, and open the one solution that had been built (on another machine) with VS2005. This works fine. I close VS2005, change the working directory in VAULT back to C:\MSNET I open VS2003, and the source bindings for the VS2003 solution are now correct again; I can work on this solution. I close VS2003 If I goto VS2005 at this point, and open the VS2005 solution file, it changes the working directory of ALL projects referenced in this solution to C:\MSNET2005 I have to remember to go back into VAULT and reset ALL the working directories back to C:\MSNET This may be by design, but I don't think VS2005 should be changing working directories without at least warning you that it is doing so.

[kadorken]

Above testing was done on vault 3.1.0 (3494)

[kadorken]

My last experiment was to go simply into VS2005, checkout 1 source file located in a project within a solution, UNDO the checkout and quit VS2005.

Checking in vault, the working folder for both the Project folder, and the Solution folder were set to the 'MSNET2005' variant. I reset the solution folder to 'inherit' from its parent and force all subprojects to do the same to
correct the problem.


As an aside, the reason for attempting the above was to test converting the application to VS2005 from VS2003, using a different directory on my same machine (the virtual machine I was using was abysmally slow ) ; I was going to Disconnect from vault in this alternate directory for the test to avoid polluting our repository with test code although we do have one library that has both a xxx.csproj (VS2003) and xxx2005.csproj (VS2005) sharing the same library source that I was using to share the library source within my virtual machine from Vault.

[ehammersley]

I can't duplicate this in the current 3.1.1.3506 version. If you haven't tried updating I would. I replayed your steps in Ladybug and couldn't make it happen.

[dan]

I don't believe there is much we can do about this. When we get instructions from VS to change working folders (be it 2003 or 2005), we can't second guess it, or a lot of other worse problems would happen.