Group items tagged

One of the things my team has been working on has been a new view engine option for ASP.NET. ASP.NET MVC has always supported the concept of "view engines" - which are the pluggable modules that implement different template syntax options. The "default" view engine for ASP.NET MVC today uses the same .aspx/.ascx/.master file templates as ASP.NET Web Forms. Other popular ASP.NET MVC view engines used today include Spark and NHaml. The new view-engine option we've been working on is optimized around HTML generation using a code-focused templating approach. The codename for this new view engine is "Razor", and we'll be shipping the first public beta of it shortly.

"In general, you should avoid building strings of HTML in your applications. There are plenty of template/view engines that are much more suitable for generating dynamic markup. However, there are some situations that require you to build snippets of HTML from code (e.g., view extensions in FubuMVC or HtmlHelper extensions in ASP.NET MVC). HtmlTags is the best way to build those snippets."

Alternative AJAX frontend for Asp.Net MVC applications

Simplify dynamic JavaScript UIs by applying the Model-View-View Model (MVVM) pattern.

"backbone.js from DocumentCloud is a small (2KB, packed) open-source library which allows you to apply the MVC (Model-View-Controller) principle to your JavaScript applications. Backbone supplies structure to JavaScript-heavy applications by providing models key-value binding and custom events, collections with a rich API of enumerable functions, views with declarative event handling, and connects it all to your existing application over a RESTful JSON interface."

"Spark is a view engine for Asp.Net Mvc and Castle Project MonoRail frameworks. The idea is to allow the html to dominate the flow and the code to fit seamlessly."

Looked at Spark about a yaer ago and it seemed ok - better than the webforms one. Started using Razor very recently and it is just amazing.

Yup, been using Razor in MM for the last 9 months or more, and it is awesome! But I read this, yesterday, that's why I tagged it: http://geek.ianbattersby.com/2012/01/07/battle-of-heart-vs-mind-you-win-again-razor-over-spark

"The Model-View-Controller (MVC) pattern is an architectural design principle that separates the components of a Web application. This separation gives you more control over the individual parts of the application, which lets you more easily develop, modify, and test them."

"Many Web applications require a way to restrict access to some resources (such as specific pages) so that those resources are accessible only to authenticated users. The default Web application project template for ASP.NET MVC provides a controller, data models, and views that you can use to add ASP.NET forms authentication to your application. The built-in functionality lets users register, log on and off, and change their password. For many applications, this functionality provides a sufficient level of user authentication."

"Model-View-Controller (MVC) is probably the most cited example of an architectural software pattern. It was conceived by Trygve Reenskaug working in the SmallTalk group at Xerox Parc in 1978. One motivation for the pattern was the separation of concerns: to allow Model objects to be concerned only with modeling business capabilities, not with how their data and methods were presented to the user, nor with capturing or responding directly to user inputs.[1] "

"Naked Objects MVC combines the power of the naked objects pattern with Microsoft's ASP.NET MVC 2 framework. Now you can take a POCO domain object model and turn it into a fully-functional web application in minutes, without writing a single line of user interface code. You can then customise the generic user interface by adding custom style sheets, custom views and custom controllers, following standard ASP.NET patterns."

Handy to pass more than one model to a view

" Naked Objects takes a domain object model, written as POCOs but following a few very simple conventions, and dynamically creates one or more complete user interfaces for it, using reflection (not 'code generation' or 'scaffolding'). It is highly effective in support of Domain-Driven Design, OO Modelling, and/or Agile Development. Naked Objects MVC builds upon the core framework to create a complete web-based user interface, using ASP.NET MVC 3. The generic user interface may be customised via the .CSS, by adding custom views, or custom controllers, as needed. Entity Framework is used to persist objects on a database. Security may be handled simply via Forms Authentication and attribute-based authorisation, or more comprehensively via Microsoft WIF and an STS. "

ASp.net Sprite and image optimization framework. Works for Asp.net MVC3 and Asp.net webforms 4