1 / 23

Enhancing ASP.NET MVC with Custom View Engines and HTML DSLs

Discover the power of ASP.NET MVC's extensibility through custom view engines and HTML domain-specific languages (DSLs). This advanced topic explores how existing libraries can serve as effective view engines, allowing built-in and custom view engines to coexist seamlessly. You'll gain insights into controlling rendering, exposing APIs as views, and the significance of the IViewEngine interface. Whether you are familiar with MVC concepts or diving deeper into rendering mechanics, this session provides valuable coding principles, demos, and a deep dive into different view engine architectures.

azure
Télécharger la présentation

Enhancing ASP.NET MVC with Custom View Engines and HTML DSLs

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DEV345 Writing an ASP.NET MVC View Engine Louis DeJardin Principal SDE Microsoft

  2. This is a great extensibility point • You can implement a new HTML DSL • Existing libraries can become good view engines • Built-in and Custom ViewEngines can coexist • You can take control of rendering • Most ActionResults are View or PartialView • All Html.Partial calls pass through IViewEngine • You can expose APIs as views • @Html.Partial(“AdBlock”, new {Zone=“Banner”})

  3. That said… • This is an advanced topic • Assumes familiarity with most MVC concepts • The nuts and bolts can be boring detailed • Several stable, production-ready options exist • This is rarely the simplest approach

  4. Where does this fit in? • MVC • Controller builds Model • Model passed to View • The IViewEngine renders the View • Well known view engines • WebForms (.aspx, .ascx) • Razor (.cshtml, .vbhtml) • Third-party (Spark, NHaml, NVelocity, etc.)

  5. The entire API: on one slide • ViewEngines.Engines • Add • IViewEngine • FindPartialView • FindView • ReleaseView • IView • Render

  6. A “Claymore” View Engine What’s the least you need to output html? demo

  7. Working well with others • Good news: it’s easy to do right • Returning searchedLocations is vital • The order of ViewEngine.Enginesis significant • Pay attention to useCache!

  8. Return IView when useCache==false

  9. Hit useCache==true only on 2nd+ calls

  10. Never jump the gun

  11. Following the rules What do you need to follow the rules? demo

  12. What View Engines typically do • Typically based on template files • Most have a mix of literal HTML and code • Some have interpreted code • Others use actual C# compiler • Some have an inspired approach to “Literal HTML”

  13. Getting views from files Rendering markdown from .md files demo

  14. Things you’ll want on your IView base • Context and ViewData • ViewDataDictionary • ViewContext and friends • Support for Helpers is great • HtmlHelper Html • UrlHelperUrl • AjaxHelper Ajax • Output methods • Write and WriteLiteral • Auto-Encoding is a Very Good Idea

  15. Bulking out the base View class demo

  16. Code: bringing templates to life • Need something to control output • Output expressions • Conditional code, loops, etc. • Many different approaches are taken • CLR languages via CodeDom or BuildProvider • Other syntaxes, compiled or interpreted • This is often the key differentiator

  17. Parsing, generating and compiling demo

  18. What have we done? • Create a new View Engine • Took care of searchedLocations and useCache • Avoiding common problems • Provided an factory _cache • Instantiated from templates from files • Turned an existing template library into a view engine • Parsed and compiled template files

  19. Web Track Resources • http://www.asp.net/ • http://www.silverlight.net/ • http://www.microsoft.com/web/gallery/ • http://www.iis.net/ • http://weblogs.asp.net/Scottgu/ • http://www.hanselman.com/blog/

  20. Resources • Connect. Share. Discuss. http://northamerica.msteched.com Learning • Sessions On-Demand & Community • Microsoft Certification & Training Resources www.microsoft.com/teched www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers http://microsoft.com/technet http://microsoft.com/msdn

  21. Complete an evaluation on CommNet and enter to win!

More Related