We have discontinued this product because newer ASP.NET versions already include a similar attribute-based routing mechanism.
This section contains a live summary of all the release notes for MVC Extensions, starting from the most recent version.
Release notes for MVC Extensions v1.x
Released on Thursday, January 17, 2013
Support for partially-trusted callers; starting with this version, MVC Extensions can be used with the default medium trust policy provided with the Microsoft .NET Framework.
Breaking change: because of the new partial trust support, the effect of the priority for the declarative routes is limited to the specific set of elements a route has been registered with, by way of a single RegisterRoutes() call. Priorities of routes defined in subsequent RegisterRoutes() calls do not interfere with each other.
Released on Monday, January 7, 2013
New support for action rendering through the declarative routing model, with the new Html.Action<TController>(controller => controller.Action(...)) and Html.RenderAction<TController>(controller => controller.Action(...)) methods support.
Added distinct assemblies for ASP.NET MVC version 3 and 4, which allows for an easier deployment of the library which doesn't require version policies. Despite of this, the two versions expose the same features.
Fixed an issue with the view finder abstraction model.
Released on Friday, December 7, 2012
Added support for type constraints for [RoutePart] parameters; the Constraint property of the RoutePart attribute now can be a type (provided it has a parameterless constructor and implements IRouteConstraint).
Added support for route URL suffixes, for [RoutePart] parameters: the new UrlSuffix property of the RoutePart attribute now allows to define custom portions of the route URL, which are added just after the parameter placeholder.
Added support for injecting custom logic for locating views (including partial views as well), by way of the IViewFinder interface; the default view finding logic is included in the new DefaultViewFinder type.
Released on Thursday, October 25, 2012
Added support for locating views for declarative routes within MVC areas.
Released on Friday, October 19, 2012
New extension classes for HtmlHelper: now with support for RouteLink() and BeginRouteForm(), with generics/lambda support for MVC action resolution.
Enhanced support for routes built on MVC actions with nullable parameters: the routing engine is now capable of handling these types in a more natural way, dispatching requests to a given MVC action only if the values coming from the RequestContext can be coerced to its nullable parameters types.
Released on Friday, August 10, 2012
Better overall interoperability with Routing Assistant
Released on Friday, June 29, 2012
Added ViewsLocation property for the Route attribute, which allows to define a custom location for the views of a given MVC action
Added the ability to remove the default parameter constraint for a given type, in the TypeDefaultConstraintRegistry type
The routing information displayed via the Visual Studio integration now correctly reflects the colors eventually configured in the IDE itself
Updated user guide for the product
ASP.NET Routing Explorer now shows only the projects with routing capabilities instead of every project in the active solution (less clutter leads to a better development experience)
ASP.NET Routing Explorer now shows the number of routes for each loaded project
Fixed a multi-threading issue with the Visual Studio integration
Released on Thursday, June 14, 2012
Added (experimental) support for Visual Studio 2012 Release Candidate