TFS Power Tool for VS 2017 to access TFS 2012 - tfs

I am working in Visual Studio 2017 and connecting to Team Foundation Server 2012.
What version of Visual Studio Team Foundation ServerĀ  Power Tools I should use so it will work as VS2017 --> TFS2012
If possible please provide link to download..
Thanks.

The power tools no longer exist in VS 2017. The stuff like the process template editor is a separate extension. Things like templating were baked into the web now.

Related

Using Source Control Explorer in Visual Studio 2022

Source Control Explorer is what I have used in the past to manage my Team Foundation version control (TFVC).
In Visual Studio 2019 (and earlier verions), you could open Source Control Explorer by navigating to View | Other Windows | Source Control Explorer. However, this window can't be found here in VS2022.
Has this functionality been completely removed or is there still a way to access Source Control Explorer using Visual Studio 2022?
Follow below steps to add the TFS server:
Manage Connections -> Connect to a project option in the Team Explorer (use View -> Team Explorer if not available) and connect to the project.
Click Add Azure DevOps Server, input tfs server URL and choose Add.
Then the list of projects you have access will be listed below, select a project and connect.
Then the Source control menu option will be made available in the usual place View | Other Windows | Source Control Explorer.
These are the steps from Visual Studio Professional 2022
Use Team Explorer for Visual Studio 2022 only when Visual studio Developer not installed.
You're probably looking for the Team Explorer.
See also Compatibility:
Team Explorer for Visual Studio 2022 will connect to Azure DevOps Server 2019, Team Foundation Server 2017, Team Foundation Server 2015, Team Foundation Server 2013, Team Foundation Server 2012, and Team Foundation Server 2010 SP1.
Yes, Cloud Explorer which is in Visual studio 2019 as shown below, has been retired in Visual Studio 2022
Instead, we can use the following alternatives mentioned here https://learn.microsoft.com/en-us/visualstudio/azure/vs-azure-tools-resources-managing-with-cloud-explorer?view=vs-2022
Go to File > Clone Repository > Team Explorer > Manage connections.

How to connect Visual Studio 2019 to TFS?

Visual Studio Professional 2019 looks to be all set for use of Azure DevOps.
We are using Azure DevOps but also have a large code base still in TFS.
I was using Visual Studio 2017 Enterprise (with TFS) but it seemed this was a 90 day trial.
I have now been issued with Visual Studio Professional 2019.
I should be able to connect Visual Studio Professional 2019 to TFS also ?
How do I do this?
Richard suggested:
Team | Manage Connections then click on manage connections, from where you can connect to servers. "Connect to a Project" form/dialog ..
thanks for this comment !
i.e. in Visual Studio Pro 2019, the option is "Add Azure DevOps Server" even though wanting to add TFS server.
i.e.
In Visual Studio Pro 2017, it looks like this:
At first I have tried (successfully) File, Source Control menu options.
i.e. File | Source Control | Advanced | Open From Server ..
Question then was: "How do I switch Visual Studio Pro 2019 from TFS back to Azure DevOps?"
I have been using Git Gui and Git Bash for working with Azure DevOps so this wasn't so important.
I worked out how to switch between TFS and Azure DevOps projects also via use of this dialog form:

Visual studio 2017 unable to connect to TFS 2008 URL

I'm unable to connect TFS 2008 URL from VS2017; Is there any patch or providers needs to be installed
Googled alot about msscci provider,
but there isn't anything specific for 2017!
I keep a blogpost with the most up-to-date information on which versions of Visual Studio connect to what and which things you need to have installed. TFS 2008 has been out of support for a while now (April 2018) and Visual Studio 2017 can't connect to it anymore as a result. Team Explorer 2010 is the last version that officially supports connecting to this old TFS version.
In order to work with TFS 2008, you need Team Explorer 2010 or lower installed and use that for your interactions with TFS 2008. This does mean that you won't have any working Team Explorer or Source control integration in the Solution Explorer.
It's highly recommended to upgrade TFS 2008 to TFS 2018 or the soon to be released Azure DevOps Server 2019. Or, take away the maintenance burden of having to run your own servers, by migrating to Azure DevOps in the cloud. The process to migrate does require an intermediate upgrade to TFS 2018 though, so I'd start with that regardless.
What to download and install for:
Team Explorer 2010
Correct TE 2010 download location
Team Explorer 2008

ProvisioningImportEventsCallback in TFS 2017(on-prem) when importing work item type definition

I'm trying to import modified WITs to a existing project. But, It was showing the below error:
Microsoft.TeamFoundation.WorkItemTracking.Server.ProvisioningImportEventsCallback
Earlier it was working fine. But, now the issue started.
What could be the possible solution for this? I just wanted to upload WITs through Command prompt(witadmin.exe) only. Any hints/information would help
From your description, you are trying to use VS 2015 to connect to TFS 2017. Please check documentation Import, export, and manage work item types:
If you are connecting to TFS, you must use the same version of Visual
Studio or Team Explorer as TFS. For example, if you connect to a TFS
2017 instance, you must connect from Visual Studio 2017 or Team
Explorer 2017.
TFS 2018 and TFS 2017
Visual Studio 2017 or Team Explorer 2017 client:
%programfiles(x86)%\Microsoft Visual Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer
or, TeamExplorer, Professional or Enterprise in place of
Community, depending on the version you've installed.
You should install VS 2017 or Team Explorer 2017 to run this command. Although VS 2015 could run witadmin command against TFS 2017 sometimes, there would have unexpected issue.
However, I found the solution for this issue by myself.
Clear the Team Foundation cache from your server and the user system from the below path:
C:\Users\\AppData\Local\Microsoft\Team Foundation\7.0 (or 6.0)\cache
Delete everything from the cache folder and restart the server\system. Then Login to the server. Now, you won't get any error for uploading [WITs] using command prompt.
Follow the procedures as given in Microsoft Site.
https://learn.microsoft.com/en-us/vsts/work/customize/reference/witadmin/witadmin-import-export-manage-wits?view=tfs-2018

TFS 2017 installation (publication) of the plugin (project) for TFS

How to publish a project developed in VS 2015 for the TFS 2017 server itself?
If you mean to create a Team Foundation Server plugin, you can reference this article : How to create and debug a Team Foundation Server server-side plugin, it's similar for TFS 2017.
And this video tutorial : Create TFS Plugin
For write TFS extension, please see this article:
Write your first extension for Visual Studio Team Services

Resources