Monday, June 11, 2012

Patterns for ASP.NET MVC Plugins: Routes, Controllers and Configuration

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 post focuses on routes, controllers and configuration. Subsequent posts will focus on other aspects, such as views, models, localization, etc.
  1. Routes, Controllers and Configuration
  2. View Models
  3. Demo: Implementing a contact form plugin