Undo Checkout - 2005 client behavior is different from prior

kjedrusiak · Post by **kjedrusiak** » Fri Sep 28, 2007 8:44 am

In VS2005 I double-click a class file.

The code window opens. As soon change the file, it gets checked out automatically. (So far so good.)

I change my mind and decide I don't want that change.

With the 2003 client...

I clicked Undo Checkout. The checkout gets un-done and the local file automatically reverts to the repository version and the file gets reloaded into the editor window in VS2005.

With the 2005 client...

I clicked Undo Checkout. The checkout gets un-done and the local file automatically reverts to the repository version, but VS2005 never reloads the file...the edit window still shows my changes. (If I try to close it will ask if I want to save changes.)

I want tio make the Undo Checkout work like the 2003 client.

Beth · Post by **Beth** » Fri Sep 28, 2007 1:15 pm

What version of Vault are you on?

kjedrusiak · Post by **kjedrusiak** » Fri Sep 28, 2007 1:18 pm

Sorry, 4.0.4

Beth · Post by **Beth** » Fri Sep 28, 2007 1:36 pm

In VS 2005, are you using the VSIP interface (VS 2005 client) or the MCSCCI interface (VS 2003 compatible client) as set in the Tools - Options - SCC?

(I ask become some don't realize VS 2005 doesn't automatically go to using the VSIP interface.)

kjedrusiak · Post by **kjedrusiak** » Fri Sep 28, 2007 1:39 pm

I was still using the 2003 client and just switched the sloution over to the 2005 client.

That's when I noticed that it was working slightly differently.

Beth · Post by **Beth** » Fri Sep 28, 2007 2:13 pm

Try performing the undo change from the pending changes window instead of solution explorer and let me know if that made a difference.

kjedrusiak · Post by **kjedrusiak** » Mon Oct 01, 2007 6:43 am

The Vault Pending Changes window is empty.

Yet the project shows on the tree as being checked out.

Interesting

A followup...something weird is going on. As soon as I closed this window after writing my initial response, the file then showed up in the Pending Changes window. (Not sure why it took over a minute to register in that window.)

When I did Undo Checkout from the Pending Changes window, it specifically asked me if I wanted to overwrite the file with the baseline version.

BradleyUffner · Post by **BradleyUffner** » Mon Oct 01, 2007 12:11 pm

I have this issue also, and a few others. I posted about it in this thread
http://support.sourcegear.com/viewtopic ... highlight=

I was told in that thread that a fix was coming in a future version.

ian_sg · Post by **ian_sg** » Mon Oct 01, 2007 12:54 pm

The issue here is that the pending change window doesn't update until the relevant files are saved to disk. A save always happens before a get or commit so there's no chance of missing a file you intended to get or check in, it's just a little disconcerting if you're closely watching the pending changes window while you work. If the pending changes window doesn't show what you expect, a CTRL+SHIFT+S (save all) will update it.

It's made more confusing by the fact that an explicit checkout immediately updates the pending change window while in implicit checkout (made when you start editing a file) does not.

Both of these issues will be addressed in future releases.