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.
Good day!
I’m planning to upgrade WebForms application and I have two possible choices:
Write it in ASP.NET MVC 2.0 with WebForms view engine and upgrade it to 3.0 when it will be out
Write it using ASP.NET MVC 3.0 RC with Razor as view engine
It seems that Razor is the only 3.0 feature I really can take advantage off for this task.
The launch date for application is Q1 of 2011 so there is a chance that ASP.NET MVC 3.0 will come out as RTM.
So, is Razor mature enough?
From what I’ve read I don’t think upgrading a 2.0 app to mvc 3.0 will be that difficult. So I am sticking with the stable code for now, and then upgrading once a stable release of 3.0 is out. I think it will be just as much work to start with 3.0 and then fix all the little changes upon the actual release of it.
Bottom line for me is that MVC 2.0 is fully functional and works with few issues. They have not called 3.0 a stable version yet for a reason.