I've just downloaded and installed visual studio express 2013 for windows desktop.
I'm working behind a proxy with username/password authentication and I don't find how to register the product (witch is now active for 14 days).
Each time : 407 - Proxy Authentication Required
I tried editing the WDExpress.exe.config to add in the section
<defaultProxy>
<proxy
usesystemdefault="true"
proxyaddress="http://x.x.x.x:8080"
bypassonlocal="true"
/>
but it's nor working.
This solution works for Visual Studio 2017 but can be adapted to similar errors and applications. Can be used as a general method to Visual Studio proxy errors, just changing processes and locations. UPDATE: It works for Visual Studio 2015 too. You must configure one process only.
Follow the next steps:
You can use a lightweight IDE like SharpDevelop to create the dll. In ShareDevelop, click in File->New->Solution and select the category C#/Windows Application/windows User Control Library. Name the application as AuthProxy. Create one class named AuthProxyModule.cs and put this code inside:
In "USERNAME" and "PASSWORD" you should set with the correct values for you. Also you should configure the right URI (in the example, proxy:8080) Build the solution and you can get the AuthProxy.dll in the solution/bin/Debug folder. This step is based on this site.
Copy the Authproxy.dll file to this directories:
Then Add the code below between and tags:
to this XML config files in the directories from the step 2 respectively:
Monitoring with Fiddler. In Fiddler, the column Process shows devenv or servicehub.identityhub or servicehub.settingshost. The process which generates the request.
The column Result shows 407 when an error occurred. The 200 is shown when it is working. The connections HTTP/1.1 will return 407. The connections HTTP/1.0 should return 200. If not, you must check the config file associated to the process.
In the Inspectors tab, click on Auth view for the request and Headers view for the response. It is a simple way to understand what it is happens.
Notes: Keep in mind that if you upgrade Visual Studio, devenv.exe.config file is modified and
<system.net>
is automatically changed by the installer to:You should reconfigure the processes.
This solution seems complicated but it works for me and allow me understanding and monitoring what is it happens.
Go to your visual studio folder, search for the devenv.exe.config file, search for
<system.net>
tag and replace it with the following: