Since releasing the first Beta we have been busy working through the issue list and have included a number of enhancements and bug fixes in Beta 2. We are hoping this will be the last Beta before the final release, and will be putting a hold on changes in the meantime to the keep the codebase stable. It would be great to make the release available early in the new year, so please grab the latest packages and let us know if you have any problems.
Those of you that follow the Autofac Google Group will no doubt be aware that despite some changes in project leadership plenty of work has been going into the 3.0 release. With the amount of refactoring that has been done we wanted to make a Beta release available for wider testing before declaring 3.0 stable. I want to take this opportunity to give a big shout out to my partner in crime, Travis Illig, who has been in there smashing through the issues with me.
This post outlines the new features in the latest pre-release NuGet packages for the Autofac integrations with MVC 4 and Web API. You can find more information about the initial support for dependency injection with Web API controller instances in my previous post.
I have released updated NuGet packages and downloads for Autofac. The core library only has a couple of updates: a new module scanning feature and some performance improvements for the .NET 4 build. The ASP.NET MVC 4 and ASP.NET Web API integrations have also been updated to the RC version.
The question of how to selectively resolve a service at runtime was asked on the Autofac Google Group recently, and since this is not the first time the question has been asked I thought it would be a good idea to write a post for future reference. There are a couple of ways of doing this but I am going to outline one that does not require you to take a dependency on the container (more specifically the component context).
With the beta release of ASP.NET MVC 4 and the ASP.NET Web API being released a few weeks ago, I decided it was about time to have a look at what the integration story would like for Autofac. The package is available for download on NuGet.
Following the release of Autofac 2.6.1, the Autofac MVC 4 Beta integration is now ready for downloading via NuGet. I will look into what additional features might be possible later, but the immediate priority was to make something available ensuring people could starting enjoying Autofac with MVC 4 Beta. This work is currently being done in a branch and will be merged back into the mainline once the final RTW of MVC 4 is made available.
The current mechanism for performing property injection on
FilterAttribute instances via the
ExtensibleActionInvoker had to be removed recently due to a rather nasty bug. These are the notes that Nick provided outlining the problem he discovered (possibly with the help of the exciting new Whitebox profiler).
The increased support for dependency injection in ASP.NET MVC 3 includes the ability to have your view pages created by your favourite container.
I have just checked into trunk a first pass at the ASP.NET MVC 3 Beta integration for Autofac. In hope of simplifying the requirements for those getting started with the integration I wanted to prevent the need to: