Roll back to a file version / Delete an unwanted checked in.

Roll back to a file version / Delete an unwanted checked in.

• vecoder

  G'day,

  From the options you have specified:

  1. It is not possible to remove revision from history in TFS

  2. I do not quite understand what you mean by merging within file history; history is not a subject to branch/merge operations

  3. There is TFS power toy application that supports Rollback operation (which looks as the one you want). Have a look at Buck Hodges blog for details.

  Hope that helps.

  Yours truly, Eugene

  
  
  

• Jwrayth

  This is hillarious, rollback not a regular thing So because it is not a regular operation is that why it is not included I can name you a thousand other features in TFS which is definately not a regular feature, yet it is included. Are you telling me our company had to pay thousands of dollars for a source control solution which cannot even support a basic feature such as rollback to version 'X' This is bad man, I mean really bad.

  I am beginning to question the design brains at M$, geez. Who would have thought of a solution that can tell you where you are coming from but gives you no option to go back there It is a basic feature in Visual Sourcesafe !

  Very dissapointed here.

  
  

• Modeller

  Destroy is exactly what we're looking for. Just a simple, very easy to find and use "oh ***" button when something gets checked in that shouldn't have.

  I'm very glad to hear it's coming.

  
  

• jigsaw-ols

  I think the key word in your post is sometimes - rolling back to specific revision is not that frequent operation. Undo latest change on the other hand is readily available.

  And as for 3rd party utilities - if they are readily available and solve the problems, I think that may be to the tool advantage rather than otherwise. From my personal experience, while there are some features not available out of the box, TFS is extensible to a very high degree. Of course, that's my personal opinion.

  Yours truly,

  
  
  

• eroe

  To be clear: Destroy is coming in Orcas. Rollback is not.
  
  I think eugene meant "undo pending change". To undo something that's already checked in you have to use tfpt rollback.
  
  

• Konstantin_T

  Note: what SourceSafe and some other source control systems call "rollback" is really "destroy" -- they permanently delete the last N changes. Destroy will be available in Orcas (check out the CTPs).

  A more generalized rollback is high on the list for the subsequent release.

  
  

• Brett H.

  HI

  Very strange - every problem or need in VSTS is solved by a 3rd party utility/script.

  Roll back looks for me a basic operation in source control (I have a backround with lots of tools) if this simple operation is so complicate to do , I think VSTS is not ready yet.

  Somtimes , I want to have the flexability to take a history version rolloing it back or merge it to the top of trunk or other branches - should be simple like in other tools.

  
  
  

• François Paradis

  As the MS author above pointed out (if not in these words), it's not there because they can't control if you roll back more than one version and lose some changes you want to keep.
  
  It seems to me that if someone wanted to roll back a change, they would be aware that they will lose all changes after that version. Even if they're not, you can show them a dialog box that says "Hey, if you do this, you're going to lose all changes made after the version you're rolling back to was checked in!!!"
  
  It's just unnecessary hand-holding on their part.
  
  

• AdamusTheGreat

  I think you are mistaken - rollback is a natural operation. I don't say it should be frequent but it shouldn't be that painful how it's done on TFS v1.
  

  In waterfall rollbacks are sinonim of a disaster because changes are painful as painful current TFS Version Control wroflows.
  

  In agile environment course switching are naturally embraced and hence should be supported. I am not talking here about rolling back a bunch of bad code - when you have good policies and continuous integration, such a code shouldn't even never get to the version control database. I am talking about rolling back on user request. If you have two-weeks iterations it's OK to allow user to change his/her mind sometimes. Current TFS version control doesn't support truly agile development process.

  And a thing I don't llike in TFS (in this rollback situation inparticular): Microsoft again tries to dictate me my process. Please don't! Dev teams could decide what's natural for the process and what's not by themselves...
  

  
  

• MarkBosley

  Rolling back a change that's not the latest is going to be complicated regardless of whether TFS adds a specific feature for it. As the original poster notes, it will require a 3-way merge. Let's say the file history looks like:
  
  100 <- last known good
  ...
  120 <- change we want to rollback
  ...
  130 <- unrelated change
  132 <- unrelated change
  ...
  [latest]
  
  In this case, we want to pass the following to our 3-way merge program:
  base = 120
  theirs = 100
  yours = tip
  
  In TFS you'd do it like so:
  tf view file;120 > base
  tf view file;100 > theirs
  tf view file;T > yours
  diffmerge /merge theirs yours base output
  
  That's exactly what tfpt does. If you're lucky there won't be any conflicts; if there are, tfpt will launch your configured diff/merge tool. Frankly I don't see how to make the process any simpler without compromising safety -- nothing involving 3-way merges should ever be trusted to a completely automatic process.
  
  

• dmc7198

  I read above that "undo latest change" is easy to get to, but I've looked for it and can't find it. How easy can it be if someone looking for it can't find it I don't see it when I right-click a file, and I don't see it when I look at a file's history. Where is this "undo latest change" feature

  I have to agree with many of the posters here - rollback is a definite must-have. I'm glad to hear it's coming in Orcas.

  
  
• Roll back to a file version / Delete an unwanted checked in.