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

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.

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,

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

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.