Question

i already built some web applications using asp.net MVC 3 and they work well, and currently i am in the state of starting a new web application for a medical clinic ; but i need to have some advice if i should consider using asp.net MVC 4 beta version instead of asp.net MVC 3?
thanks in advance for any help and suggestions ?
BR

Answer 1

Personally I would start in MVC3 and then upgrade the project to v4 when it’s RTMd. Previous versions have had some issues when migrating from Betas (altho see update below).

You can be sure, however, that as with previous version increments, a swift and easy upgrade path will be available (usually there’s a project conversion tool released at the same time).

I have a project I’m working on right now, and if I get to the web layer before v4 is finished, I’ll be starting in v3 first.

I suppose it does depend, however, on whether any of the new features, such as the adaptive rendering via Mobile views (or indeed the Web API), are intrinsic to your solution. Just don’t release on a beta platform 🙂

Update July 2012

I ended up getting to the web layer of my current project before v4 RTM so decided to go to the RC release first; then the nightly nuget packages for Web API support.

Apart from editor issues (that are documented), I’ve found no issues, even with integrating a whitelabelling extensibility library I’ve written, for MVCs 1-3, that operates at a very low level.

Would I have migrated early if I’d not needed the numerous benefits that the Web API provides? Probably not.

But as it is, I’m glad I did 🙂