Pending change sets visible across vs.net solutions

martillodecampo · Post by **martillodecampo** » Wed Sep 12, 2007 8:40 pm

I'm using Vault 4.0.4 with VS.Net 2005 on xp2 and am using the Vault VS.net 2005 client on all solutions.

Here's a sample scenario illustrating this issue:

I open up two instances of VS.Net and load Solution A into the first one and Solution B int the second one.

I check out some files in Solution A. Then I move to Solution B and notice that the files I checked out in Solution A are listed in the Vault Pending Changes window in the instance of VS.Net that has Solution B loaded into it.

If I go back to A and check in the files and then return to B, the previously checked out files from A are still listed in B's Vault Pending Changes window, with no way to refresh the view.

This is a little disconcerting to see another solution's checked-out files in the pending checkin window. Is this by design?

Also, yesterday I opened up a solution file in notepad for a solution I was having this problem with and noticed that it was actually referencing the file path for another solution. Since that particular project was only a few days old I just recreated it to clean things up.

ian_sg · Post by **ian_sg** » Thu Sep 13, 2007 7:53 am

The pending change uses working folder assignments to determine what changes to list. What's the repository path for each solution and it's projects? Do they share any projects? Do you have a working folder assignment that's a parent of both?

For example, this arrangement:

$/MySolutions [Working Folder: c:\work]
$/MySolutions/Solution1
$/MySolutions/Solution2

results in changes for both Solution1 and Solution 2 being shown if you're working on either one.

martillodecampo · Post by **martillodecampo** » Thu Sep 13, 2007 3:50 pm

Thanks Ian.

If I understand correctly what you're explaining, then yes, this is my situation. I have a parent folder called "Source Control" and all my source-controlled solutions are organized beneath it. I've set the working folder association for the parent Source Control folder and checked the box to have working folder associations cascade down to child folders, which is a great convenience. In my experience, a lot of developers set Vault up this way.

I've been using Vault for years like this and I know that the VS2003 compatible client only showed checkouts that pertained to the current solution.

I think it's nice to be able to see pending checkins across all solutions in the Pending Change Set window displayed by the Vault client, but when working on a specific solution with VS.net it makes more sense to me to have that view restricted to files that pertain to the current solution.

I suppose I could resolve the issue by resetting my working folder associations, but that seems like an inconvenience.

ian_sg · Post by **ian_sg** » Thu Sep 13, 2007 3:54 pm

You're right, of course.

This is a scenario we want to support. The issue is not yet scheduled for a particular release, but we do intend to support it.

In the mean time, I apologize for the inconvenience of having to set additional working folders.

martillodecampo · Post by **martillodecampo** » Thu Sep 13, 2007 3:56 pm

Ok, thanks. As a faithful Vault customer I will wait patiently for that golden release...