Is there any risk associated by using asp.net mvc 2 on production or stick to the asp.net mvc 1.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is there any risk associated by using asp.net mvc 2 on production or stick to the asp.net mvc 1.
It is (ready). Telling that from experience.
Most trouble are with 3rd party tools (i.e. – spark hack).
Took me like 1 day to migrate completely our web app to Mvc2 RC (which ain’t giant).
Asp.net Mvc has quite nice suite of unit tests and really good architecture – therefore, it’s kind a stable, there aren’t much breaking changes (faced only one in Mvc2 RC => viewcontext demands textwriter as last argument or something. Normally – that shouldn’t be a problem and you wouldn’t even notice that (not for me, cause i had mechanism that renders html as string). And there might be some issues with validation (our app is quite
read-only)).Related blog post from our fellow member Craig. 🙂
Recently (current date => 2010-02-06) Mvc2 RC2 was announced.
Main changes – validation