Tuesday, July 24, 2012

Patterns for ASP.NET MVC Plugins: View Models

The goal of these patterns is to provide a consistent experience for plugin consumers (application developers), minimize the amount of configuration required to get a plugin working in the host application and maximize the plugin's flexibility to customize its behavior.

This is the second post of the series, see also the other posts:
  1. Routes, Controllers and Configuration
  2. View Models
  3. Demo: Implementing a contact form plugin