Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an existing ASP.NET MVC 2 application that is working well and is usually easy to maintain. I had a lull in development yesterday so I upgraded the solution to ASP.NET MVC 3 and everything appears to be working.

I've been researching ASP.NET MVC 3 and there are a number of improvements including the Razor view engine, integrated support for unobtrusive JavaScript, etc.. These all seem interesting but not necessarily for an existing application that already has dumb views, unobtrusive JavaScript with jQuery, dependency injection, unit testing, etc..

What ASP.NET MVC 3 features, if any, could have the greatest impact on an existing MVC 2 application?

share|improve this question
up vote 1 down vote accepted

None really. v3 is just a minor update.

However I do find global filters very interesting, so that you don't need to apply them to every controller.

Aside from that, even if you don't upgrade to v3 I advice you to put in a fresh version of jQuery (v3 comes with 1.4.4).

share|improve this answer

I would only update an existing application to a new framework (not just MVC3) if there were known bugs that were fixed in the newer version. Otherwise why risk it? You would need role out new DLLs (not too hard) and retest your app, which is more of a pain.

I think the approach of installing it in a local environment is valid for testing and investigation. You can always release future versions against MVC3, but don't risk breaking an existing application.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.