[Original] ASP. NET error: Unable to connect to ASP. NET developement Server

Error Background:
When debugging a web project in vs2010, a prompt is displayed: Unable to connect to ASP. NET developement server. Then it will no longer work. You cannot open the browser to run the project and enterHttp: // localhost: Port, and cannot connect to the project. The final result is that the project cannot be debugged and the running effect cannot be seen.

Note: The Web server in vs2010 runs well and can be opened automatically and allocated ports.

Analysis Error:
I searched the internet over and over again, and tested N Methods: turning off the firewall and anti-virus software did not help, or even uninstalled the anti-virus software. The last re-installed vs, the cup is still reproduced.

Everyone knows that Microsoft is very annoying, especially useful things such as Vs and sqlserver, which basically cannot be detached.

In the end, there was no way to directly reinstall the system. I had to reload the system for the cup. The cup happened again and the error still exists. However, it is different from the previous one. In the past, all web projects failed to run. Now one of them can run and I was given a bit of toiletries.

Analysis can run and cannot run projects: So how to analyze? It should be analyzed from the csproj project of the web. The results are a little different. The final result of the web. csproj file of the project that can run is as follows:

<Projectextensions>
<Visualstudio>
<Flavorproperties guid = "{349c5851-65df-111089384-00065b846f21}">
<Webprojectproperties>
<Useiis> false </useiis>
<Autoassignport> true </autoassignport>
<Developmentserverport> 4504 </developmentserverport>
<Developmentservervpath>/</developmentservervpath>
<Iisurl> http: // localhost/Web </iisurl>
<Ntlmauthentication> false </ntlmauthentication>
<Usecustomserver> false </usecustomserver>
<Customserverurl>
</Customserverurl>
<Saveserversettingsinuserfile> false </saveserversettingsinuserfile>
</Webprojectproperties>
</Flavorproperties>
</Visualstudio>
</Projectextensions>

Overwrite the text of this section to the corresponding node of the project web. csproj file that cannot be run, and run the project OK again.

Solution:Add the preceding XMLCodeCopy and overwrite a project that cannot runCorresponding node of the web. csproj File

TIPS:
Some Microsoft software problems cannot be explained in many cases. Sometimes, even if the problem is solved, why ???
In short, the problem that has been plagued for a week has been solved!