Unsetting working folder vs. pending change set problem

This forum is now locked, since Gold Support is no longer offered.

Moderator: SourceGear

Posts: 52
Joined: Thu Mar 08, 2007 3:49 am

Unsetting working folder vs. pending change set problem

Post by Tilman » Thu Sep 13, 2007 2:59 am


I'm having a problem with un-setting working folders in the GUI client (Vault 3.5.2). Whenever I do so, files that are in the working folder and in the pending change set are not removed from the pending change set.

I would expect those files disappearing from the pending change set, as for example, in the 'Contents' panel the files are now shown as missing.

When I then try to manually delete the files I get an error saying 'Object reference not set to an instance of an object.'

So to remove the files from the pending change set I then have to re-set the working folder (or remember not to un-set it in the first place) then undo the changes or do a 'get latest', and then un-set the working folder, again.

Since, I'm using CVS mode to avoid lots of check outs, and since as the build master I work on a lot of different projects, I set and un-set working folders a lot, to avoid the pending change set cluttering up, i.e. I encounter this problem a lot. And it is also confusing other users that I try to convince to use CVS mode.

Please, could that be fixed in a future version?



Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear

Post by Beth » Thu Sep 13, 2007 8:09 am

I just ran a test of that in Vault 3.5.3 and the pending change disappeared when I unset the working folder. Right now the beta of 3.5.3 is available. Information on how to get the beta is posted here: Vault 3.5.3 Beta. In another 1-3 weeks I believe the final release will be available on our downloads page.

Posts: 485
Joined: Sat Mar 13, 2004 9:00 am

Post by GregM » Thu Sep 13, 2007 8:33 am

I've run into that a couple times recently. I had to delete the CacheMember_KnownChanges file from my client side cache to get one of the files to go away, since the file no longer existed on my disk.

Client Information
Vault Client Version:
.Net Framework Version: 2.0.50727.832
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 2 GB
Time Zone: (GMT-05:00) Eastern Time (US & Canada)

Server Information
Vault Server Version:
.Net Framework Version: 2.0.50727.42
Operating System: Microsoft(R) Windows(R) Server 2003, Web Edition
Service Pack: 1.0
OS Version: 5.2.3790
Timezone: (GMT-05:00) Eastern Time (US & Canada)
SQL Version: Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear

Post by Beth » Thu Sep 13, 2007 3:43 pm

Thanks for the additional info Greg. After Vault 3.5.3, the changes we made in that release will get merged into the 4.x version, unless it was something specific to only the 3.5.x versions.