This project is read-only.

Release Notes

v1.0.1 - March 28, 2013

Added DtoModelBinderProvider which is more efficient, factoring out some of the reflection from the request cycle. If the DTOs that you are using as models are only wired up once (not variable implementations) then use these two wireup declarations in your MVC app:

// Let FlitBit.Wireup know we are dependent upon DTO
// causes our DTO implementations to be emitted/compiled at wireup time.
[assembly: WireupDependency(typeof(FlitBit.Dto.AssemblyWireup))]

// Add a ModelBinderProvider that can bind DTOs (factors out some reflection; faster).
[assembly: WireupDependency(typeof(FlitBit.Dto.Mvc.AssemblyWireupAddModelBinderProvider))]

Otherwise, in cases where 1) you implement FlitBit style DTOs (always interfaces), and 2) you supply custom implementations of those interfaces in different scenarios, use these two wireup declarations in your MVC app:

// Let FlitBit.Wireup know we are dependent upon DTO
// causes our DTO implementations to be emitted/compiled at wireup time.
[assembly: WireupDependency(typeof(FlitBit.Dto.AssemblyWireup))]

// Replace the DefaultModelBinder with one that can bind DTOs (more reflection, adaptable to types
// that do not exist at wireup, or implementations that are swapped out at runtime).
[assembly: WireupDependency(typeof(FlitBit.Dto.Mvc.AssemblyWireupReplacingDefaultModelBinder))]

v1.0 - March 27, 2013

Initial release. Replaces MVC 4's DefaultModelBinder with one capable of binding DTOs (based on FlitBit.DTO.

To make it work your project will need:
  1. Wireup declarations found here
  2. Global.asax.cs must kick-off the wireup process similar to what is found here

~P

Last edited Mar 29, 2013 at 4:23 PM by cerebralkungfu, version 2

Comments

No comments yet.