I suggest you ...

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...)

3,429 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    SergioSergio shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    completed  ·  Visual Studio TeamAdminVisual Studio Team (Product Team, Microsoft) responded  · 

    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

    Matt
    Program Manager | TFS Version Control

    167 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • SS commented  ·   ·  Flag as inappropriate

        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.

      • SRGSRG commented  ·   ·  Flag as inappropriate

        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.

      • Anonymous commented  ·   ·  Flag as inappropriate

        I have to buy a new version just to get back something simple that worked fine on previous versions?! Really?!

      • MaximMaxim commented  ·   ·  Flag as inappropriate

        Incredible... "We returned old pending changes window, all you need to do is to buy VS 2013" ;) Thanks a lot.

      • Anonymous commented  ·   ·  Flag as inappropriate

        The link you posted to the preview build is broken. It should not have "here:" in front of the real link.

      • Randy BrattonRandy Bratton commented  ·   ·  Flag as inappropriate

        I don't have the option that some other developers have of going back to VS2010. My company says I HAVE to use VS2012, so this is going to be one PITA once I have to start checking in change sets. I have to exclude certain files because I work remotely, so these can NEVER be checked into the Team's TFS.

      • Moon FisherMoon Fisher commented  ·   ·  Flag as inappropriate

        One of the reason that VS-TFS UI integration is so pathetic is that MS developers don't use TFS internally.

        They use source depot, which is one of the best source controls I have ever seen.
        They need do dogfood it more thoroughly.

      • Moon FisherMoon Fisher commented  ·   ·  Flag as inappropriate

        To Sean Bergam on MultiSelect:

        This is a very lame reason to use VS 2012. You can do it easily (and more intuitively) in VS 2010.
        Just multi select your files (using space/shift/Ctrl+A... whatever) and press space.

        Also, VS2010 has a tree view option in Pending Changes also, why can't VS2012 have a listview too?

      • Moon FisherMoon Fisher commented  ·   ·  Flag as inappropriate

        Pending Changes in VS 2012 is a complete ****. In fact VS 2012 in whole is so non intuitive that it is unusable. MS forgot that VS is a developer tool, and developers need to know their changes in a plain view, WE know what we are doing.
        DON'T try to teach us what we are doing.

        The other big pain point is shelving/unshelving.
        I am using VS 2010 just because the UI designers of VS2012 are mentally ********.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Argument-less comments such as "I like it" or "I dislike it" should be dismissed as a subjective personal like or dislike.

      Feedback and Knowledge Base