This problem it seams is to do with the way Visual Studio 2010 connects to your TFS server over HTTPS. The default value for “BypassProxyOnLocal” in Visual Studio 2008 was “False”, but it has been changed to “True” for Visual Studio 2010 Beta 1. It should be noted that this is currently a Beta 1 workaround and this behaviour may be updated for Beta 2 and RTM.
You can fix this by adding the following registry keys and restarting Visual Studio 2010:
You need to add a “RequestSettings” key to both of the following location that contains a string value pair of “BypassProxyOnLocal=’False’”.
32bit OS Key Locations:
1HKEY_LOCAL_MACHINESOFTWAREMicrosoftTeamFoundationServer10.0RequestSettings
2
3HKEY_LOCAL_MACHINESOFTWAREMicrosoftVisualStudio10.0TeamFoundationRequestSettings
64bit key locations:
1HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftTeamFoundationServer10.0RequestSettings
2
3HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftVisualStudio10.0TeamFoundationRequestSettings
You can find out more on the “ How to: Change the BypassProxyOnLocal Configuration ” documentation on MSDN.
No related videos found.
If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.
We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.
Lockheed Martin
Slicedbread
Ericson
DFDS
Genus Breeding Ltd
SuperControl
Graham & Brown
ALS Life Sciences
Bistech
Brandes Investment Partners L.P.
Healthgrades
Epic Games
ProgramUtvikling
Microsoft
Slaughter and May
Freadom
Hubtel Ghana
Milliman
Department of Work and Pensions (UK)
Washington Department of Enterprise Services
Royal Air Force
Nottingham County Council
New Hampshire Supreme Court
Ghana Police Service
Kongsberg Maritime
SuperControl
Boeing
Big Data for Humans
Higher Education Statistics Agency
YearUp.org