My favorites | Sign in
Logo
                
Search
for
Updated Aug 04, 2009 by nicholas.blumhardt
Roadmap  
Release plans.

Introduction

Autofac 1.4 is the current version.

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

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

1.2

Status: Released

Release Date: 20 May 2008

Internal implementation improvements. More extensibility. More consistent behaviour. Better performance. Minor feature additions.

(Original integration features were rescheduled and expanded. These will now be implemented in the Autofac Contrib project on its timeline instead)

1.3

Status: Released

Ongoing maintenance not binary-compatible with 1.2.

1.4

Ongoing maintenance not binary-compatible with 1.3. Aligning codebase with goals for .NET 4.0 support.

Since 1.4.4:

  • Arguments can be specified for Open Generic and Automatic registrations
  • ResolvedParameter type added - flexible parameter handling for reflection-based registrations
  • Non-generic overloads added for generated factories
  • Overloads for ResolveOptional() passing service name added
  • ContainerProviderContainer added to Autofac.Integration.Web

2.0

Keep Autofac current, taking advantage of and responding to advances in .NET development technologies.

Status: Planning


Comment by gphatw...@yahoo.com, May 21, 2008

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.

Comment by nicholas.blumhardt, Jun 27, 2008

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.


Sign in to add a comment
Hosted by Google Code