When working on multi-developer projects, if each developer machine isn’t configured the same way developers can waste a lot of time editing connection strings, local machine name, and other settings when pulling code projects from source code control. On ASP.NET code projects, you can configure per-machine configuration overrides to overcome this.
Many ASP.NET 2 projects will have utilised the AJAX Control Toolkit for more dynamic behaviours and the performance gains of partial page refreshes. A common issue with having used that toolkit when upgrading an ASP.NET 2 project to ASP.NET MVC is how to replicate the controls it offered without adding a lot of additional work to the upgrade project.
Although ASP.NET MVC3 can be deployed on a machine running Windows Server 2003 and Internet Information Services 6 (IIS6), the practice isn’t recommended and hosting multiple MVC3 web applications can be a painful business. If you are committed to this approach though, here are some instructions to configure IIS6 so that you can deploy a MVC3 website.