Menu
Visual Studio automatically tries to connect to Team Foundation Server on startup but sometimes when you frequently change TFS servers it takes a long time for Visual Studio to timeout on its attempt to connect to the last used TFS.
How can this be disabled?
603
On September 10, 2018, Microsoft renamed Visual Studio Team Services (VSTS) to Azure DevOps Services. With Azure DevOps Server 2019, Microsoft is renaming Visual Studio Team Foundation Server to Azure DevOps Server.
Source Code Control: Team Foundation Server is a Version Control System. It enables the team to manage all source files or artifacts for a project. It allows the developers to store the files in a centralized repository (database). It helps to maintain different versions of source code.
Q: Does the Visual Studio Code extension support Team Foundation Server (on-premises)? A: Yes! With version 1.103. 0 the extension supports Team Foundation Server 2015 Update 2 and later.
You can set AutoLoadServer registry key to 0.
Navigate to Team Foundation key
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\TeamFoundation
Add a registry key AutoLoadServer of type REG_DWORD
Set the value to 0 so that VS doesn't connect to TFS automatically on startup
Or create a *.reg file with the following:
Visual Studio 2010
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\TeamFoundation] "AutoLoadServer"=dword:00000000
Visual Studio 2013
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0\TeamFoundation] "AutoLoadServer"=dword:00000000
Visual Studio 2015
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\14.0\TeamFoundation] "AutoLoadServer"=dword:00000000
131
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
