Razor vs Webforms view engine for new ASP.NET MVC 3 site

asp.net-mvc asp.net-mvc-3 razor viewengine
BritishDeveloper picture BritishDeveloper · Mar 10, 2011 · Viewed 31.8k times · Source

Razor is prettier (and is new therefore cool).

Webforms is something I am already familiar with.

Naturally I would unquestionably go for the new thing to learn - Razor. But I have heard of two disadvantages that worry me:

  • can't easily reuse existing web forms controls - in the rare instance I may need to drag something across... I'll reiterate - 'RARE'
  • I hear it is less efficient at rendering (takes longer than web forms)

So what are the advantages of Razor over Webforms view engines when using ASP.NET MVC 3?

Answer

marcind picture marcind · Mar 10, 2011

This has already been addressed by the following question: Does Razor syntax provide a compelling advantage in UI markup?

Related questions

How do you declare a comment using the Razor view engine?

Using ASP.NET MVC's default view engine, you can declare a server-side comment like this: <%-- This is a comment --%> This comment will only be visible on the server side and is not sent to the client. …

Read More
ASP.NET MVC: Multiple View Folders and _ViewStart.cshtml file

I have an MVC project that requires there to be 2 different View folders. One is at ~/Views/ and one at ~/Framework/Views/. This is done by creating a custom view engine based on the razor view engine like this: public …

Read More
HTML.ActionLink vs Url.Action in ASP.NET Razor

Is there any difference between HTML.ActionLink vs Url.Action or they are just two ways of doing the same thing? When should I prefer one over the other?

Read More