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.


Comments (4)

  1. Rob Caron says:

    Eric Lee has resuscitated his blog (For shame, I’ve been a lazy blogger!)! For those unfamiliar, Eric…

  2. Eric Lee on be careful of proxy settings when using the Team Foundation Server Object Model, KPI and…

  3. buckh says:

    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