I\'ve got vs2010 and vs2012 installed side by side. If I open up our MVC site in vs2010 and run it using the development web server it works fine, if I do the same thing in vs2
In your Project --> Right Click Properties then select Web option in your left side in the Servers section check Use Local IIS Web Server
** Config.XML is the first place to begin research ** on new Windows Visual Studio 2012 install. The values should be manually reviewed on each new client/server application
When truly inappropriate server errors make no sense at all, think about your test computer's config XML files that set queue or pool sizes explicitly in the project root, as described in the above MS link. It's highly odd that a server would respond "Too Busy" when it's just you on the machine.
Always good to be able to reuse as many recyclable objects as possible, in particular, database connections.
As far as running both VS 2010 and 2012 on the same development machine it should be ok. Just check there your references are pointing for application dlls.
You have to raise the concurrent request limit. Read the following :
Modifying the ASP.NET Request Queue Limit http://technet.microsoft.com/en-us/library/dd425294%28office.13%29.aspx
If you are running debug in Visual studio with a particular port number, try changing port number. Probably something went wrong with your port on web server.
just clean the solution before you build it. Also, check the size of the folder in which the solution is, before & after clean build; you will surely find some difference. Doing this ensures that you clean/remove unnecessary dlls created after every build which is the cause of delaying the normal flow.
If you need to increase the request limit for IIS Express try this:
Configure Maximum Number of Requests in IIS Express