Razor CSHTML - Any Benefit over what we have

Question

Anyone out there using the new CSHTML pages feature and is finding that they prefer this new view engine syntax over the existing ASP NET MVC default view engine or over web forms  and if so  why   What about CSHTML gives you an advantage over MVC or web forms  or vice versa   Just curious to hear people s take on it

User · Answer

Everything is encoded by default     This is pretty huge  Declarative helpers can be compiled so you don t need to do anything special to share them   I think they will replace  ascx controls to some extent   You have to jump through some hoops to use an  ascx control in another project  You can make a section required which is nice

User · Answer

Ex Microsoft Developer s Opinion  I worked on a core team for the MSDN website  Now  I use c  razor for ecommerce sites with my programming team and we focus heavy on jQuery front end with back end c  razor pages and LINQ-Entity memory database so the pages are 1-2 millisecond response times even on nested for loops with queries and no page caching  We don t use MVC  just plain ASP NET with razor pages being mapped with URL Rewrite module for IIS 7  no ASPX pages or ViewState or server-side event programming at all  It doesn t have the extra  unnecessary  layers MVC puts in code constructs for the regex challenged  Less is more for us  Its all lean and mean but I give props to MVC for its testability but that s all   Razor pages have no event life cycle like ASPX pages  Its just rendering as one requested page  C  is such a great language and Razor gets out of its way nicely to let it do its job  The anonymous typing with generics and linq make life so easy with c  and razor pages  Using Razor pages will help you think and code lighter   One of the drawback of Razor and MVC is there is no ViewState-like persistence  I needed to implement a solution for that so I ended up writing a jQuery plugin for that here -  http   www jasonsebring com dumbFormState  which is an HTML 5 offline storage supported plugin for form state that is working in all major browsers now  It is just for form state currently but you can use window sessionStorage or window localStorage very simply to store any kind of state across postbacks or even page requests  I just bothered to make it autosave and namespace it based on URL and form index so you don t have to think about it

User · Answer

The biggest benefit is that the code is more succinct   The VS editor will also have the IntelliSense support that some of the other view engines don t have   Declarative HTML Helpers also look pretty cool as doing HTML helpers within C  code reminds me of custom controls in ASP NET   I think they took a page from partials but with the inline code   So some definite benefits over the asp net view engine   With contrast to a view engine like spark though   Spark is still more succinct  you can keep the if s and loops within a html tag itself   The markup still just feels more natural to me   You can code partials exactly how you would do a declarative helper  you d just pass along the variables to the partial and you have the same thing   This has been around with spark for quite awhile

User · Answer

One of the benefits is that Razor views can be rendered inside unit tests  this is something that was not easily possible with the previous ASP Net renderer   From ScottGu s announcement this is listed as one of the design goals      Unit Testable  The new view engine implementation will support the ability to unit test views  without requiring a controller or web-server  and can be hosted in any unit test project     no special app-domain required

[c#] Razor/CSHTML - Any Benefit over what we have?

Examples related to c#

Examples related to asp.net-mvc

Examples related to razor