ASP.NET MVC2 Is Here - To Upgrade or Not ?
Mar
25
Written by:
3/25/2010 2:15 PM
Those of you who know me understand that I like new technology. I don't need to be on the absolute bleeding edge, but close to it. So, when Microsoft released ASP.NET MVC2 earlier this month, my interest was piqued. I discussed this new offering with a client who has engaged me to update his project management web application. He left it up to me to upgrade from MVC1 to MVC2.
On one hand, it's good to stay current and keep the application using the most recent codebase. This is especially true if MVC2 offers new bits that will make the project run more smoothly. However, on the flip side, is it really that crucial to go to the next version so quickly? The answer really depends on the application and whether it would benefit extensively from the MVC2 bits.
The jury is still out on this one. My advice would be to use MVC2 for any new projects stared from scratch. I suggest careful evaluation of existing MVC1 projects to see if they merit the update to MVC2. If it's not broken, don't fix it as the sayin goes.
Happy Coding,
WebDBApps