I have TFS Power Tools 2012 installed on my PC.
I recently uncloaked a project in TFS and performed a get operation to bring the project folder into my private workspace (using server-side for backwards compatability with VS2010).
Whilst in Visual Studio, there is no problem - I can check it out and check back in.
However, Power Tools does not recognise the new folder in windows explorer. In other words, all other projects have the green-arrow icon overlay, but this one doesn't. Right-clicking on the folder also does not bring up the TFS context menu.
Does anyone know what I may have neglected to do? I have tried deleting the folder and doing a "Get specific..." to bring it back in. Hell, I've even done a repair on TFS Power Tools and restarted; the behaviour remains unchanged.
This is not my problem (the rest of my projects do show the icon overlay)...
Possible duplicate here maybe...
I have noticed Power Tools sometimes has conflicts with icon overlays, particularly when they compete with others (like SVN).
It can also conflict when you have multiple workspaces on your PC. As you mentioned, make sure the project is uncloaked in both workspaces.
Related
I am using Visual Studio 2013. Regarding TFS workflow, there are issues I have when working on a bug or work item, after I am finished, I move the changes into a shelfset for further review, undo my changes by right clicking on the pending changes and clicking undo. The move on to the next issue or enhancement. The shelfsets can be indpendendly reviewed and then applied to whatever branch they are currently needed.
The problem I have is that undoing through visual studio does not completely reset the solution to a completely clean state. There are often orphaned files around or projects that have references to non-existing files or other such problems. I'd like to be able to completely nuke and reset my solutions from source control as if I am a new developer and I have not found an easy solution to do this.
Currently, the only way I can accomplish this is to go to "Source Control Explorer" remove the file system mapping for the project. Go to the file system, removed the folder. Go back into "Source Control Explorer" add the mappings back in. And then "Get Latest Version".
Is there an easy way to completely reset a solution in Visual Studio with TFS?
You can achieve this in Visual Studio 2010 without Power Tools. Process is likely similar for other VS versions.
Open the Source Control Explorer. Right-click the entry you want to reset, then choose "Get Specific Version." Select the version you want to reset to. Ensure that the two checkboxes are checked:
☑ Overwrite writeable files that are not checked out
☑ Overwrite all files even if the local version matches the specified version
This will overwrite all locally mapped files with the server's version. (And will correspondingly take time proportionate to the number of files.) I do not believe that this operation will remove any unmapped files.
If you have the Power Tools installed, call tfpt scorch /deletes /recursive /diff. That should make your local folder match the server exactly.
You can also call tfpt treeclean, which will just delete any item that is not mapped to TFS. It won't update or replace any changed files though, like scorch will.
We have upgraded our TFS from 2010 to 2013, and the same time moved the TFS and databases to new servers, with new names.
One of the very few annoying effects (Probably due to moving the TFS to a server with a new name) is that the build controller/agent from the old server is still visible in lists of available build controllers/agents, but is not visible in the admin gui for build configurations and therefore not possible to remove.
Does anyone have had the same experience and furthermore have a solution of how to remove the traces of old (and not used/wanted) build controllers/agents?
Kind regards,
J
Ok.
Sorry, I found the solution myself now after continue searching and yet again scanning through the microsofts documentation! :)
It's possible to disable and delete controllers and agents through the Manage Build Controllers in Visual Studio.
Also described here: http://msdn.microsoft.com/en-us/library/ee330987.aspx
Just make sure there is no builds in progress, but that's ofcourse also possible to handle through Manage Queues in Visual Studio.
We have several of our projects at my company in source control using Visual Studio Team Services (visualstudio.com). For the life of me I can't figure out how to get the workspace on my machine to flip to a Server workspace type. We don't want multiple checkouts and we want to get latest when we edit a file, and server workspaces (as I understand it) are the only way to accomplish this. Is it even possible to use server workspaces with the "cloud" version of TFS/Visual Studio Team Services?
Thanks!
Connect to your server with Visual Studio
Go to Team Explorer
Go to Settings
This part can be a little tricky so I attach a screen shot:
Under "Team Project Collection" go to Source Control
On the new dialog go to the second tab - Workspace Settings
So as you can see it is pretty obscure and I believe it is on purpose. By default the workspaces are of type "local" and these have their benefits. You may want to check out this article to make an informed decision: http://msdn.microsoft.com/en-us/library/bb892960.aspx
We're a small shop and have legacy VB6, Classic .ASP, .NET 1.2 - 3.51. We installed the product successfully, but since depending on the code which needs changing we fire up the respective IDE Visual Studio x. How do we go from no source control to TFS?
You will probably want to look at the TFS 2008 Power Tools. One of the features that is available in the Power Tools is Windows Explorer integration, so you can get/checkout/checkin by right clicking the file(s).
Your other choices are to use the VS2008 / TFS 2008 client to do your SCM operations (which means you need to switch between multiple IDEs), or you could use the TF.EXE command line to do your SCM operations.
If I misread your question and you're asking how do you get your legacy code into TFS, you'll need to go into the TFS 2008 client and do the following:
Map a workspace to a folder on your hard drive (or network).
Copy your source to the folder.
In TFS 2008, click on the "Add Files" button.
Select the folder you just copied everything into.
Add them.
Check in.
I have a solution which I developed in VS2008 and which I am trying to add to Source Control (TFS 2010, though the issue happened in TFS 2008 as well). I have several TFS workspaces on my computer and I have access to several Team Projects.
When I right click the solution in my Solution Explorer and choose the "Add Solution to Source Control" option I am never given an option of choosing which Workspace or which Team Project to add the existing solution to. VS2008 then proceeds to add it to the same team project every time. I have tried selecting an alternate workspace/team project in every window where I can see an option for it but it always adds it back to the same one. I even tried changing the name of my new workspace so that alphabetically it was the first thinking that it might be somehow related to that; no luck.
I then tried going to the Change Source Control window where you can add/remove bindings on a solution/project but that window also defaults to the same Team Project as trying to add the solution directly does.
In my experience, the add to source control mechanism tries to use the physical path of the solution to determine which TFS project it belongs to. You could try to move the solution by right-clicking on the solution folder in the Source Control Explorer and choosing "move" to move it to the TFS project of your choice.