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.
I’m just getting into ASP.NET web pages with Razor. Based on what it has to offer, would you choose it for your application? It seems to me the ASP.NET MVC framework gives Razor more of an edge because of everything MVC has to offer; it’s nice that the web pages framework has some helper components from the WebMatrix DLL, but most of the examples having all the code in one file, plus the reliance on a new set of API’s (via webmatrix) is a turnoff to me.
What do you think?
Thanks.
Razor View Engine + ASP.NET MVC is a great combination. Razor definitely seems like the view engine of choice most of the time because it is syntactically much easier to read and work around than ASPX. This benefit alone is huge because you can have developers that are solely focused on HTML and UI development, and have them be able to work around the syntax.
The biggest problem with Razor so far has been it’s intellisense support. But, it looks as if the latest version of ReSharper solved that problem nicely, and I’m sure the support for Razor will continue to get better.