I bought a new Windows 8 PC last week.
First I installed VS 2010 on it but then that wasn\'t working properly so I uninstalled VS 2010 and then installed VS 2012 pro
All right. I had this problem for a week and I have tried many solutions. Finally, the following procedure will fix the problem.
I have set the Firewall system manually. This means that, at the time of communication by programs Firewall notify me. Incorrectly linked to "devenv.exe" was blocked by the Firewall. Correct mode of communication "devenv.exe" will solve the problem. "devenv.exe" is located in the following path.
"C: \ Program Files (x86) \ Microsoft Visual Studio 12.0 \ Common7 \ IDE \ devenv.exe"
Devenv lets you set various options for the integrated development environment (IDE), and also build, debug, and deploy projects, from the command line.
Enjoy...
I've run into the same general error message that you stated, but the details of my error included the following:
Unable to connect to the configured development Web server.
Failed to register URL “http://10.10.7.209:53553/“ for site “FooBarSite” application “/“. Error description: The format of the specified network name is invalid. (0x800704be)
The fix for me was to make changes to the applicationhost.config
file located in C:\Users\Jed\Documents\IISExpress\config
Specifically, I had to update the bindingInformation
for the site so that the IP Address matched the IP Address of my development computer.
Instructions
ipconfig
to determine the IP Address of your computerC:\Users\Jed\Documents\IISExpress\config\applicationhost.config
(in Notepad)<sites>
, then find the <site>
that has the name of your project (in this example it was FooBarSite
bindingInformation
so the IP Address matches the IP Address that was determined in ipconfig
Example
<bindings>
<binding protocol="http" bindingInformation="*:53553:localhost" />
<binding protocol="http" bindingInformation="*:53553:10.10.7.209" />
<!-- I had to change the IP Address from 10.10.7.209 to 10.10.7.214 -->
</bindings>
ASP.NET IIS Registration Tool (Aspnet_regiis.exe) would be one of my suggestions along with checking what identity is the Application Pool in IIS using as it may have limited permissions. Last but not least, run Visual Studio as an Administrator so you don't have UAC issues.