Welcome to MSDN Blogs Sign in | Join | Help

Be careful of proxy settings when using the Team Foundation Server Object Model

Someone may have already blogged about this, but I didn’t see it.  When using the Team Foundation Server Object Model, be careful what you set your connection properties to.

I had some code like:

TeamFoundationServer tfs = TeamFoundationServerFactory.GetServer(“mustang”);

WorkItemStore wit = (WorkItemStore) tfs.GetService(typeof(WorkItemStore);

I noticed a long, long delay when getting my WorkItemStore object – almost 30 seconds in most cases.  The problem was that in my LAN settings (under Internet Explorer -> Tools) was set to automatically detect settings. 

For some reason, when I ran this code at home, I experienced this long delay.  It was generally OK on my network at home.  When I changed this setting, everything worked fine.

Anyways, I spent a few hours tracking this down, so I wanted to share it in case anyone was running into the same thing.

Eric.

Published Friday, July 07, 2006 11:32 AM by ericlee

Comments

# Eric Lee is Blogging Again!

Friday, July 07, 2006 7:51 PM by Rob Caron
Eric Lee has resuscitated his blog (For shame, I've been a lazy blogger!)! For those unfamiliar, Eric...

# VSTS Links - 07/10/2006

Monday, July 10, 2006 9:31 AM by Team System News
Eric Lee on be careful of proxy settings when using the Team Foundation Server Object Model, KPI and...

# re: Be careful of proxy settings when using the Team Foundation Server Object Model

Wednesday, July 12, 2006 1:00 PM by buckh
See the ByPassProxyOnLocal setting at http://blogs.msdn.com/buckh/archive/2005/12/12/503015.aspx for controlling this without changing the IE settings.

Buck

# Visual Studio Team System Blog, Johannes Jauch, VSTS, Axinom GmbH

Anonymous comments are disabled
 
Page view tracker