Using Source Control Explorer in Visual Studio 2022 - tfs

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.

Related

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:

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

Powerbuilder 2017 with Team Foundation Server

How can I implement TFS in Powerbuilder 2017 ??
Do i need VisualStudio?
The goal is to use TFS for version control
Steps in brief
Setup the team explorer 2013 (use this link if you do not have visual studio subscription to download team explorer 2013 ) in the machine you are running PowerBuilder to get the TFS connectivity capability to your machine. You do not need to install Visual Studio.
Install MSSCCI provider in the machine to allow power builder to access TFS version control
Create a team project in team foundation server
Connect Power Builder workspace to TFS by going to Properties of workspace and source control. Set the TFS as source control and provide the credentials to connect.
For more details you can follow the instructions in https://community.appeon.com/groups/powerbuilder/using-powerbuilder-2017-tfs-source-control

TFS Power Tool for VS 2017 to access TFS 2012

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.

How to connect AX 2009 with Visual Studio Online (Visual Studio Team Services)

I'm trying to connect my AX 2009 installation to VSO (recently renamed to VSTS).
After browsing some forum entries I know that I have to install the following:
Install Visual Studio 2008 (not the Express Edition)
Install Team Explorer 2008
Install Visual Studio 2008 SP1 (This will upgrade both VS2008 and Team Explorer 2008 to SP1)
Install VSTS 2008 Forward Compatibility Update
The installation order is important because the SP1 will update VS and Team Explorer, so I followed that order.
Then I created a project in Visual Studio Online.
Now I want to connect my AX 2009 with the repository in VSO. The VSO is hosting a TFS, so this should work.
As far as I could find out to configure the TFS settings you need to set the Version Control Parameters and the System Settings. I did both as shown in the following screenshots:
When I'm setting the Version Control Paramters the Internet Explorer opened and I needed to authenticate with my User and Password against VSO (so this seems fine to me).
The final step now would be to Create the Repository (Tools -> Developer Tools -> Version Control -> Create Repository. But when I try to do this I get the following error-log: Team Server connection error. [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
The settings in 7 could be wrong - I'm not really sure what values are to set there.
Any help is appreciated.
The plugin is trying to access a SQL Server database. As VSTS is hosted on Azure and uses multi-tenanting there is no access to SQL server on that URL.
I am pretty sure that this is not ever going to work. VSTS is NOT just hosted TFS and even if it were, Visual Studio 2008 is no longer supported as a client for either TFS or VSTS.
Install the following components:
Visual Studio 2010 with SP1 (can be installed side by side with, or as a replacement for VS2008).
Team Foundation Server 2010 SP1 Object Model
KB 2662296
KB 2736182
There's additional discussion around this on the Dynamics Community AX Forum.

Resources