|
|
Roadmap
Release plans.
Introduction
Autofac 1.2 is now available.
1.0
Establishes the concepts of mixed expressions and autowiring, automatic component disposal and implementation-type hiding as useful foundations for dependency injection in .NET.
Status: Obsolete
Release Date: Nov. 2007
- Feature-complete core
- Suitable replacement for many existing containers
- Some integrations available, enough extension points to enable any other popular integration to be done
- All future 1.0 increments will maintain binary compatibility with each other
1.1
Eases deployment into a wider variety of environments. Increases accessibility to developers and teams not wishing to build their own integration facilities and extensions.
Status: In Maintenance
Release Date: 19 Mar. 2008
- More extensibility points
- Core Mono support
- Focus on deployment - strong named assemblies etc.
- Packaging of 'extras' that may be handy but don't warrant core inclusion
- Minor interface improvements, internal refactorings & optimisations
- Largely backwards-compatible, some minor find/replace/rebuild migration
1.2
Status: Released
Release Date: 20 May 2008
Internal implementation improvements. More extensibility. More consistent behaviour. Better performance. Minor feature additions.
- Registrars now support OnlyIf(c => x) to register components selectively based on a predicate over the target container
- The additional registrar method DefaultOnly() will filter the services that a registration provides so that existing registrations will not be overridden
- IComponentRegistration exposes a Preparing event that can be used to add/modify parameters or to short-circuit the activation process
- Everything is now taggable: tags are associated with registrations using the InContext<T>(T tag) builder method
- Extended properties (for IComponentDescriptor) can now be specified in configuration files
- Constructors can be chosen for generics and automatic registrations
- Some components have moved to the new Autofac Contrib project
- Factories generated by the Autofac.Extras.GeneratedFactories extension are now threadsafe
- Circular dependency error messages are better
- IComponentDescriptor exposes a BestKnownImplementationType property
- TaggedRegistration<T> now implements the non-generic IRegistrationDecorator to make accessing the InnerRegistration member easier in advanced scenarios
- Improved error messages when IContainerProviderAccessor is not implemented correctly on a user's HttpApplication class (System.Web integration)
- Necessary hooks added for DynamicProxy2 support
- Intellisense documentation included in release zip files
(Original integration features were rescheduled and expanded. These will now be implemented in the Autofac Contrib project on its timeline instead)
2.0
Keep Autofac current, taking advantage of and responding to advances in .NET development technologies.
Status: Planning
Release Date: ~Oct. 2008
Sign in to add a comment
I very much like what I see... I believe Autofac in the .NET 3.x space. Keep up the good work! I want to use Autofac instead of Spring.NET for a new project, but require AOP functionality. Any idea when AOP will be available in Autofac (I saw the posted discusssion items), or if you recommend an AOP framework that can be used in conjunction with Autofac (e.g. PostSharp?, Castle, etc.) until the Autofac AOP is availble.
Howdy commenter - sorry no to have noticed your question earlier, these comments aren't monitored the way the Autofac Google Group is. You may be aware by now of the DynamicProxy2 implementation in http://autofac-contrib.googlecode.com. If you have any further input please post to the group.