title: ASP.NET MVC concurrent development
body: <p>I am researching the best way of establishing and maintaining a very large intranet site that will be developed concurrently by several developers who will need to make changes to different areas of the site concurrently.</p>
  
  <p>I would like to use ASP.Net MVC for this but I am concerned that it will be very difficult to use this technology as the framework requires that the site be compiled (other than the views) and the deployment process would also seemingly overwrite other changes in the test environment when a developer chose to progress a build from their development machine.</p>
  
  <p>Presently we use an interpreted language that does not force us to build the entire site to deploy individual changes....am I missing something in respect of how compiled frameworks and in particular how ASP.Net MVC works?  Or is it the case that non sequential, fast paced development by several developers will inevitably result in problems when not using interpreted code?</p>
  
  <p>Would PHP make a better choice given the nature of our workflow in the circumstances?</p>