There is a point to this story, but it has temporarily escaped my mind...
Contact Me MyFaceBook MyLinkedIn MyGitHub MyTwitter

Visual Studio 2010 Will Not Use The System's Proxy Settings

There is a new feature in Visual Studio 2010 call the extension manager. It is a great feature that seems to be sensitive to proxy servers… However, in my company I could not take benefit of the extension manager for long time. The company I work at uses a content filtering/proxy service called Web Sense. It uses some type of active directory based authentication to control access to the Internet. Although I have the proxy set in Internet Explorer via GPOs, it seemed that Visual Studio is not using those settings according to Fiddler… It turns out that the default proxy settings for .NET apps is for some reason to not use the system proxy and credentials. Visual Studio will by default ignore that proxy setting as will many other .NET applications…

I needed to configure the proxy settings in the Visual Studio config file. The section I was looking for is under <>. The config file already had this section to enable IPv6.

I modified the file with this change:

The XML for copy-paste:

  <defaultProxy useDefaultCredentials="true" enabled="true">
    <proxy usesystemdefault="True" />

This turned out to be a fairly simple fix as these settings tells Visual Studio to use the system proxy, and to use the default credentials for that proxy.I had to close Visual Studio and re-run it again for the settings to take effect.

Copyright © 2022 by Julian Easterling. SOME RIGHTS RESERVED.
Privacy Policy              Terms of Use             

Creative Commons License
Except where otherwise noted, content on this site is
licensed under a Creative Common Attribution-Share Alike 4.0 International License.

All of the opinions expressed on this website are those of Julian Easterling and
do not represent the views of any of my current and previous clients or employers in any way.

If you notice an error on the site or content that has not been properly attributed, bring
it to my attention using the contact page and I will endeavor to fix it as soon as I can.

I accept no responsibility or liability for any damages incurred by following any of
my advice or by using any of the information on my site or of those sites that I link to.