Future plans

There may not be much of a need for Unity Automapper once Unity 3 is feature-complete because, as I understand it, it will support convention-based registrations etc. which may fill in the niche that the Automapper was created for.

For the time being, I am cautious about adding much more as my main goal for this project has been to keep the API as simple as possible and to fit the 80/20 rule. One feature I may add is to provide a list of interfaces that you want mapped as a "default set", which will only use those interface supplied, but will use all types identified in an assembly as potential implementations.

If you have particular feature requests, don't hesitate to let me know.

###vNext

• Ability to specify particular lifetime managers. Currently you can specify Singletons or Transcient (default); you may have other lifetime managers e.g. Hierarchical that you want to use.
• Simple modules - the ability to go "outside" of the Automapper sometimes in a decoupled manner. A IUnityModule interface will allow you to do any custom mappings etc. on an assembly-by-assembly basis that cannot be done through guidance to the Automapper.