VS11. Bring back the old "Pending Changes" window
The new one is very confusing!!!
I think the old one was almost perfect so why did you change it??? I mean, you can add new options but why did you change the philosophy?
The most important problems I see with the new one:
- No way to have that window independent so it can be accessed easily and fast
- Difficult to see at first sight the files changed! (of course, the new “no color” interface is part of the problem...)
- Difficult to exclude changes! (in the old one it was so easy by clicking the checkbox...)
We are happy to let you know that in today’s release of Visual Studio 2013 Preview we have made numerous improvements to the Pending Changes experience. The most significant additions are the ability to undock the Pending Changes page from Team Explorer, an option for viewing changes in a flat list, text filtering, and the removal of the “All Changes” page that was used when your number of files exceeded 250 items.
You can get the VS2013 Preview build here:http://go.microsoft.com/fwlink/?LinkId=306566
Program Manager | TFS Version Control
William Bosacker commented
@EMI: You might want to look into Shelvesets. You can "shelve" all of your current changes that you don't want to check in, do a "Get Latest Version", make the bug fix changes, check in the bug fixes, then restore your shelveset, do a "Get Latest Version" to merge in any changes, and pickup where you left off.
I forgot to mention: think of my below cycle is repeated over and over again. Am I missing something out of VS2013?
The working cycle with lists in Pending Changes window is a weird one at least. I have 100+ files checked out and modified. Out of them I want only 3 to check in in a batch because they refer to the same bug but the other 100+ refer to another developments I work in parallel. So with the new cycle I have to scroll all the list of 100+ files and select just those 3 of interest to transfer them in the Include list wile keeping the other in Exclude list. Well, I forgot to mention that in my 100+ modified files there are 5 or more that I never ever want to check-in but I want to keep them always in Excluded files (they are particular settings for build which fit only for my own machine; they cannot be checked in without introducing a big fuss for the other developers). Back to MS life cycle of checking files: After making my those 3 into Include I have to check-in and after that deal with those 5 (scrolling, selecting, playing with Include/Exclude, drink coffee and begin smoking ....)
Microsoft does not use Visual Studio to develop so they do not know how bad their changes are.
Sowen Cheung commented
second that, the new Pending Changes sucks on sooooooooooooooooooooooo many levels. I always want to love Microsoft, but why the fxxk you always ***** us!!!!!!!!!!!!!!!!!!!!!!!
I agree with you SRG, it's money, but in this case they don't need to develop nothing as the checkin window exists and works perfectly (see http://stackoverflow.com/questions/12204845/vs2012-return-to-a-normal-tfs-checkin-window/14234794#14234794). The cost of making it available should not be excessive, for sure lower than the changes they made in VS2013.
Cedric, I can answer your 1st question because it touched a very simple truth in software world. No software will ever let you choose between old and new version by configuration. This is because 2 versions will have to be supported simultaneously in this case. Which is twice costs.
Why don't you let choose developers to use the new pending changes tab or the old pending changes window by configuration ?
The visual studio 2013 changes are still unusable and are a waste of time compare to the VS2010 window...
And why do you mark the post as completed if no one is happy with a solution that doesn't change anything ?
absolutely DETEST checking in anything using VS2012. I puke multiple times during it and often leave projects checked out simply because i hate it so much. 2010 was so simple. Akin to other source controls and logical. This is so horrendous and painful to use. like everything on 2012, miserable vile design and so painful to use daily.
Sandra Walters commented
My team *just* upgraded to 2012 (I've been using it personally for a while) and an upgrade to 2013 will not happen for quite some time. I fail to see how a fix for a broken feature in the 2013 Preview is going to help those of us stuck with the broken feature in 2012.
I've blogged about how you can easily still use the VS 2010 style of pending changes window when you have VS 2012 installed at http://blog.danskingdom.com/launch-visual-studio-checkin-window-with-a-keystroke/
If you want to change the design and claim its better for me in the future thats fine with me, I will get used to it but Im suprised no-one has mentioned the speed problems I have with the pending changes window, although there are far too many compaints to read them all
I find I have to wait for the pending change window to update quite regularly and cannot click on anything in the team explorer while it keeps refreshing itself, but, even assuming our repository is huge and our network is terrible and could be sped up, it ran a lot smoother using 2010.
If I click on an item to change it and the window is still loading and changes shape beneath my mouse, ( like the start page annoyigly did) then my click activates something else. If I start editing a file and want to look at its details and go to the pending changes it will take ages to load. It looks ready but I click on something and it will instantly refresh and freeze my mouse.
The diff also takes much longer to load and appear, if you use it to edit the pending changes will update themselves continually, just as you think its finished and you go to click on something, it updates itself a bit more and makes you wait again. Its not just slow, its a tease.
I assume the window is regulary checking with the source control server for information that I probably dont need right away, but its unreasonable to have to wait 8 seconds after saving a file change before I can click on anything in my pending changes window and continue my work.
Please stop integrating everything into one big slow running behemoth just to make it look shiny.
I hear the developers dont even use TFS. Make them, and they will fix it.
Steven Bone commented
After looking at the 2013 Release Candidate, I am still unhappy with the new Pending Changes window. I much preferred the tabs down the left side (instead of taking all of my vertical real estate) as well as the checkboxes to include/exclude files (combined view instead of included/excluded sections). Please take this (yet again) back to the drawing board.
Garry Star commented
I want this fix in 2012!
We upgraded a 25 solution applcition from VS 2010 to VS 2012. This resulted in ~200 modified files. Before checking in, we did a Get Latest Version from the Source Control tab and had ~40 conflicts due to recent edits by other developers.
How can we manualy merge the ~40 conflicting files given that they are across multiple solutions?
The Resolve Conflicts window will not find any conflicting files, nor does it show the workspace/solution to search for conflicts.
We need to do the manual merge first, restest locally on a dev machine, get a final code review and then check-in.
VS 2013 is alpha/beta and cannot be used for our commercially sold software until it is released into production for a few month at the earliest.
Bring it back
Even if Pending Changes were not broken in VS 2012, you would still need to buy a new 2013 version :) Looks like they are shortening release cycles for Windows and other products to be more like Apple and Google.
I have to buy a new version just to get back something simple that worked fine on previous versions?! Really?!
Incredible... "We returned old pending changes window, all you need to do is to buy VS 2013" ;) Thanks a lot.
The link you posted to the preview build is broken. It should not have "here:" in front of the real link.