viewengine - What are the benefits of using an alternate ASP.NET MVC view engine? -


I have seen the suspects as usual ... SPARC, NHAM, etc. They are syntax for all those people & lt; %%> Uncomfortable with syntax Are there any other concrete advantages? Syntactic Chinese does not consider me a reason enough to change the whole view engine.

The reasons have been posted so far:

  1. More natural context switching
  2. Better separation of concerns
  3. Low lines of code
  4. Better resistance cross-site scripting
  5. Improved XHTML compliance

Reasons people & lt; %% & gt; are not uncomfortable with syntax that contain a lot of syntactic salt, but it shows that code-centric , which can be as dumb as possible in view of the scene Against the MVC concept of Spark's goal, for example, "allows HTML to dominate the flow and to make the code perfectly fit". That's why tangible advantage is making it easy to follow the MVC's spirit.

  & lt; Viewdata products = "IEnumerable [[product]]" /> & Lt; Ul if = "products.Any ()" & gt; & Lt; Li Each = "var p" in the products & gt; $ {P.Name} & lt; / Li & gt; & Lt; / Ul & gt; & Lt; Rest & gt; & Lt; P & gt; No products available & lt; / P & gt; & Lt; / Left & gt;  

If the above syntax is Chinese, then ASP.NET MVC is the syntax Chinese at the top of the ASP.NET web form.


Comments

Popular posts from this blog

c++ - Linux and clipboard -

What is expire header and how to achive them in ASP.NET and PHP? -

sql server - How can I determine which of my SQL 2005 statistics are unused? -