So the process would flow like this: Person 1 requests a code review. Person 2 adds comments and selects “Needs Work.” Person 1 makes the necessary changes. Person 1 Updates the shelveset associated with the code review Person 1 adds comments to continue the discussion Repeat steps 2 – 5 until accepted Here are the … Read more
You can try to change your default processor architecture in your Test Setting from X86 to X64. In my case this was the problem. This happens if the platform target of your project under test is set to x64.
This is an older post, but since the only given answer seems “not entirely correct” to me I’d like to answer anyway: I blogged about this (in german) here: blog.nils-andresen.de If you have a local copy, that you want to un-get or un-download like this: simply right-click the folder and then click “Get Specific Version” … Read more
Go to Team Explorer, then “Pending Changes”, then “Actions”, then “Find Shelvesets”, then right click on the shelve you want to unshelve, finally “Unshelve”.
From VS: Open Team Explorer Click Source Control Explorer In the nav bar of the tool window there is a drop down labeled “Workspaces”. Extend it and click on the “Workspaces…” option (yeah, a bit un-intuitive) The “Manage Workspaces” window comes up. Click edit and you can add / remove / edit your workspace From … Read more
One relatively simple way to do this is: find an appropriate point in your source tree in the Source Explorer window, maybe the root of the branch but you can also drill down a bit …or, if you know a specific file that was included in the changeset then find it and select it (can … Read more
This happens when the following is in the .sln file: GlobalSection(ExtensibilityGlobals) = postSolution MyGlobalProperty = AnyValue EndGlobalSection I found that Enterprise Library added one of these. I removed it, checked in the solution, closed then re-opened it, and no more automatic check out.
What typically helps to fix it is deleting the Solution User Options aka “SUO”. VS up to 2013 In the older VS it is stored as a “hidden” SolutionName.suo in the same folder as the main .sln file. VS2015 or later In VS2015 the same data was moved to a “hidden” .vs folder under the … Read more
Use the command line utility TF – Team Foundation Version Control Tool (tf). You can get a list of all workspaces by bringing up a Visual Studio Command Prompt then changing to your workspace folder and issuing the following commands: C:\YourWorkspaceFolder>tf workspaces /owner:* You should see your problem workspace in the list as well as … Read more
Use the tf.exe tool from the Visual studio commandline – it can handle wildcards: tf.exe move <olditem> <newitem> Example: tf.exe move “$/My Project/V*” “$/My Project/Archive” [EDIT] As noted in the comments: move is an alias for rename. Both commands move history.