I am viewing the history of my TFS code warehouse, and from the change set list, I choose to view the change set details Information. On the right sidebar of VS 2012, I got a list of all changed files for this particular change set.
However, I want to open one of the files and modify them directly (basically for light Massive code review and housekeeping), so I right-clicked one and selected “Open”.
Unfortunately, this did not open a local copy of my file, but (seemingly) from the server Download the file and give me a server copy with a modified file name (short hash suffix). I cannot modify it at all.
Is there a way to open my local copy of the file from the changeset details?
< p>This is the first time I have tried this in VS, let alone VS 2012, so if the answer is common sense, I think I am not that common. (Yeap, Google also let me down – or my Google- fu only needs to be oiled.)
I am viewing the history of my TFS code warehouse, and from the change set list, I choose to view the details of the change set. On the right sidebar of VS 2012 , I got a list of all changed files for this particular change set.
However, I want to open one of the files and modify them directly (basically for lightweight code review and housekeeping), So I right-clicked one and selected “Open”.
Unfortunately, this did not open a local copy of my file, but instead (looks like) downloading the file from the server and giving me the server copy, with The modified file name (with a short hash suffix). I cannot modify it at all.
Is there a way to open a copy of my local file from the changeset details?
If you right-click and compare it with the workspace version, the difference will be opened between the workspace version and the changeset version. I don’t believe it There is a way to directly open the local version of the change set file, because the version does not really exist in the local workspace. When you open it from the change set, the specific version associated with the change set is opened. The file may not even exist In the current solution, it is not even feasible to open the workspace version under the same circumstances (or you may never get the file).