Different Behavior of "Checkin" operation between VS2010 and VS2012 RRS feed

  • Question

  • Hi,

    We found that there is a difference between VS 2010 and VS 2012.

    When we want to check-in the code in VS 2010, we right-click the files in solution explorer, and select "check in", the code change will transfer to the TFS server, good work ! no issue !

    However, when we use VS 2012, and select "check in", we will be navigated to a Pending Change window, and we have to click "check in" in Pending Change window again....

    Now our project is a plunge-in tool in VS, this behaviour really change makes us upset... Because, our user can directly use "pending change" window to check in the code. In that condition, IVsPersistHierarchyItem2.SaveItem will never be called, even IVsPersistHierarchyItem2.IsItemDirty() gives us the right answer ( tells us the file is dirty)

    Can you kindly tell us what is the code change ( i.e. interface change, method change) in Pending Change window between VS 2010 and VS 2012...

    Thank you in advance.

    Tuesday, May 14, 2013 3:02 AM

All replies