Great Tool Indeed, Use it very often and its making my day to day task easier saving lots of time, well one suggestion I would like to give is tfpt getcs <changeset> command, pl. add one more functionality to that is to get the files to a different folder specified rather than to the workspace which is mapped to
Have you installed Visual Studio on this machine? The Power Tools contain server and client components. If the Visual Studio 2012 client is not installed, the client components will not be available to you.
This is fixed in QU3. In QU2 if customers have a misconfigured Reporting Services instance, the WMI call throws an exception and the Scheduled Backups wizard fails to start. QU3 has just been released and has this fixed.
Apparently something is wrong with the version detection on this package. I have vs 2012 web express edition and applied update 1 all on a newly configured machine. A prerequisites page comes up indicating that virtually all the features require "Microsoft Visual Studio 2012 or Visual Studio Team Explorer 2012". I have seen no mention of the power tools requiring the pro edition so I can only assume the detection criteria within the msi are incorrect?
You can put [project]\Contributors as group in the validusers but when you reload the assignedto properties it's empty even thow the xml contains the correct entry <VALIDUSER group="[project]\Contributors" />
At the same time, why are only the [Global] groups offered in the drop down and not the [project] ones ?
Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.TeamFoundation.PowerTools.CommandLine.XamlCleaner.Clean(XDocument document)
at Microsoft.TeamFoundation.PowerTools.CommandLine.CommandBuildProcessTemplate.Clean(String sourcePath, String targetPath)
at Microsoft.TeamFoundation.PowerTools.CommandLine.CommandBuildProcessTemplate.<.cctor>b__28(CommandBuildProcessTemplate command)
at Microsoft.TeamFoundation.PowerTools.CommandLine.CommandLine.RunCommand(String args)
at Microsoft.TeamFoundation.PowerTools.CommandLine.CommandLine.Main(String args)
The exception occurs when mc:Ignorable contains more than 1 prefix, for example: mc:Ignorable="sads sap sap2010"
XAttribute xattribute = document.Root.Attribute(XName.Get("Ignorable", "http://schemas.openxmlformats.org/markup-compatibility/2006"));
if (xattribute != null)
this._ignorableNamespace = document.Root.GetNamespaceOfPrefix(xattribute.Value).NamespaceName; // <-- HERE, because xattribute.Value = "sads sap sap2010"
When removing the last field rule from a state, it show's like it has been removed but when you reload the workitem it's still there. You have to edit directly the xml by exporting and the reimporting to remove that last rule.
I get an warning when running BPA that not all team project admins are sharepoint site collection admins. I have TFS 2012 and SharePoint 2013. The account format in the display is different for the two systems. The team project account is "last, first". The sharepoint account is I:0#.w|domain\ntname. Is the claims based token enough to create a false warning?
Also, my TFSSERVICE shows up in the warning. It is in team project collection administrators, but not in the sharepoint sharepoint site collection admin. I'm using TFSREPORTS for the SSRS and SharePoint. Should I be removing or adding TFSSERVICE from one or the other? Thanks.
We are not planning to include any more providers in the immediate future, but it is currently possible to extend the plug-in to other providers. I know there was a project to write a Skype add-on for Team Members by a company in Germany but I don't know the current status or if it is publicly available.
The assembly Microsoft.TeamFoundation.Collaboration.dll contains a public interface, ICollaborationUIPRovider, and public classes DefaultProviderContactControl and DefaultProviderPopup that can be used for writing your own extensions. The interface and classes are commented but are provided without external documentation.
Will the latest release of the Power Tools be able to interact with Team Foundation Server 2013 Preview if I connect to Team Foundation Server 2013 Preview using Visual Studio 2012 with Update 3?
It seems that read-only files are assumed to be versioned by scorch & treeclean and therefore ignored completely from the processing of these commands. This seems particularly problematic given TFS will leave a deleted/renamed/moved file in the old (local workspace) location as a now un-versioned file that has the read-only attribute set. Is there a reason for this as it seems a little counter intuitive to me?
I tried to compare two build definitions with the TFS 2012 Power Tools. Unfortunately i always get the error message "could not load file or assembly 'Microsoft.TeamFoundation.Build.Workflow, Version=18.104.22.168, Culture=neutral, PublicKeyToken=....' or one of its dependencies. The system cannot find the file specified.". With a Team Foundation Server 2010 and the corresponding Power Tools 2010 it works fine. But it fails on a TFS 2012! I got this error on TFS 2012 Update 1 and for Update 2 as well. Can anyone help me out? Thanks in advance
I got the same error with running tfpt builddefinition. I found a solution that worked for me:
- Made sure that the command prompt had TFSPowerToolDir set to the 2012 version (mine was set to 2010 version, as the 2010 Power Tools were installed after the 2012 Power Tools; so I had to change the Environment variable)
- Went to the following path for VS2012 (default installation path on 64-bit machine)
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\PrivateAssemblies
- Copied the following files
- Went to the following path for 2012 TFS Power Tools (default installation path on 64-bit machine)
C:\Program Files (x86)\Microsoft Team Foundation Server 2012 Power Tools
- Pasted the copied files
- Re-ran my command
- The error went away
My system set up (in case it matters)
- VS2010 Ultimate (latest SPs / patches)
- VS2012 Ultimate (Update 3)
- Power Tools 2012 installed first
- Power Tools 2010 installed second
We use the windows shell TFS power tools lots but there is no output (or result) window when you perform actions such at "Get Workspace" or "Check-in". It would be great to be able to see the "Source Control - Team Foundation" output window you get in Visual Studio. There have been several times you just get a pointless error when performing a check-in. You need to run VS in order to see exactly what the error is.
Is there any way to get the output window to display in the windows shell?
Another enhancement would be to have a settings/properties window for the windows shell plugin to allow the user to connect to another TFS Server. You should need to run VS in order to create a workspace. If the folder you are currently in does not have any TFS objects then you do not get a TFS menu. Why cannot we not always have the "TFS" menu available in any folder in order to create a new workspace and connect to a TFS Server.
TFS 2012 Power Tools (base and Update 1) - The only 'Get' menu items in the 'Team Foundation Server' shell-integration menu are:
1. Get Entire Workspace
2. Get Selected Items
The all familiar 'Get Latest' and 'Get Specific Version' available in TFS 2010 Power Tools are no where to find. How to perform these functions under Explorer shell?
I am unable to remember if the "Get Specific Version" command has ever been in the Shell Extension. I looked at the history of the source code and could not find any reference that it ever existed.
Please be aware that the Shell Extensions (the context menu in the Windows File Explorer) and the Team Explorer (the pane in Visual Studio) are two different things. Is it possible that you confuse these two?
It was not there in the 2010 version of the shell extensions, but it would certainly be a great command to have in the extension. Now we still have to use Visual Studio if we moved/deleted/renamed a file in the explorer without using the delete/move/rename command from the tfs menu.
Hi, you only addressed the Get Specific Version. I am interested in the Get Latest. Is that functionality available from the shell. I tried doing Get Selected Items on the root folder and I think that may have done it but if it did, it wasn't obvious and if this is what this is for then the label on the menu is horrible. Very confusing. Thank you.
Is anyone paying attention to this thread? I will rephrase the question. IN VS Source code explorer, there is a menu option titled "Get Latest Version". I look for the same option in the power tools but there is nothing there. I do see an option for "Get Selected Item(s)". Is this the same thing? It appears to be but the label "Get Latest Version" is a bit more clear what you are doing. Thank you for any clarification.
To play devil's advocate, what else could "Get Selected Items" possibly do besides get the latest version, given that it does not prompt you for a specific version?
The "Get Entire Workspace" and "Get Selected Items" options both do a Get Latest Version. One does it for the whole workspace, the other does it for only the selected items.
There used to be a single option in the shell extension ("Get Latest Version"). There were two drawbacks with this:
1. It was unclear if the entire workspace would be updated by the Get (the most common type of Get), or only the selected items would be updated (it was the latter).
2. If you wanted to update the entire workspace, you'd have to navigate all the way back up to the workspace root and do a "Get Latest Version" from there.
3. In TFS, it is possible to have multiple root folders in a single workspace. What if you wanted to update all of them? You couldn't, without doing a separate Get in each workspace.
That's why there are two separate context menu items that do a Get Latest in the shell extension. BTW, VS doesn't have this issue, because the server root folder is always visible and right-clickable in Source Control Explorer.
If I wanted to be super clear, I could have named one menu item "Get Latest Version in Entire Workspace" and the other "Get Latest Version for Selected Items". I felt that that was too verbose. If you have a better suggestion for naming both menu items, I'm interested.