user281921
user281921

Reputation: 661

Installing Visual Studio 2017 Behind Corporate Proxy

Pretty simple problem. I'm unable to install VS 2017 RC behind an NTLM corporate proxy. I have tried running it through fiddler and fiddler + cntlm with no luck.

I have also tried creating .exe.config files for the outer (vs_enterprise.exe) and inner (vs_setup_bootstrapper, vs_installer and vs_installershell) files.

In all cases it doesn't look like the installer is trying to connect anywhere and in the few cases when it does connect, even when it gets a '200' with some data I still get a "You may not be connected to a network" error.

I'm sure that fiddler and cntlm are both working as I use them for my node/npm tools.

I don't have any 'safe' machines outside the firewall so I can't create the download there and pull it here.

Can anybody suggest any other ways of installing the software?

Upvotes: 8

Views: 21674

Answers (3)

Nicola
Nicola

Reputation: 61

The I3enners answer is correct but if you are behinde a company proxy probrably you need to add user,password and domain on the proxy addess like this:

<system.net>
  <defaultProxy enabled="true" useDefaultCredentials="true">  
    <proxy bypassonlocal="True" proxyaddress="http://domain%5Cusername:password@youproxyaddress:portnumber" />
  </defaultProxy> 
</system.net>

The '%5C' is the excape for '' . Put the code to the bottom of your machine.config in

C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config and C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config

Upvotes: 6

user281921
user281921

Reputation: 661

Looks like MS have addressed the proxy issue.Problem solved.

From the comments:
The installer now uses auto-proxy detection for downloads. from release notes of version 15.4 preview 2, September 11, 2017.
https://www.visualstudio.com/en-us/news/releasenotes/vs2017-preview-relnotes

Upvotes: 1

I3enners
I3enners

Reputation: 165

if you add

<system.net>
   <defaultProxy useDefaultCredentials="true" >
   </defaultProxy>
</system.net>

to the bottom of your machine.config in C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config and Framework64 then this should fix it. Also fixed my problems syncing to VSTS

Upvotes: 10

Related Questions