should help you out Rollback entire changeset will give you a set of Pending Changes that when checked in will "undo" what was done in changeset 601. The result is that you will have 3 changesets: 600, 601, 602. And the resulting state will be the same as after 600.
hop of those help? I resolved this issue by using a TransactionScope in an override of the Submit method in my domain service. This allows the PersistChangeSet to behave as a unit of work (in other words, changes are only persisted if all operations are successful). Details here: http://msdn.microsoft.com/en-us/library/ee707364(v=vs.91).aspx
TFS: "Get This Version" vs "Rollback Entire Changeset"
Hope this helps According to your description, you shouldn't use rollback entire changeset feature. This will influence your source control in TFS. If you roll back a file to an earlier version, tfs will eliminating the effect of all changesets that occurred after that version. More details please take a look at this tutorial: Roll back changesets Actually you just want to get an older version in history include all files for a branch or root project folder.
TFS 'Get specific version, checkout/checkin' vs 'Rollback Entire Changeset' vs 'Rollback selection of changesets' vs 'So
I hope this helps . When you right click on a file and Rollback... you got the pop-up, in the top you have the field Items to Rollback, by default the value there will be the server path to the file. So when you do rollback from there the rollback will be only to this file and not impact other files.