NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet, #111 most downloaded on NuGet
Autofac is an IoC container for Microsoft .NET. It manages the dependencies between classes so that applications stay easy to change as they grow in size and complexity.
Latest stable
9.3.4
Last release 2 months ago
18 Sep 2026
Ships fairly regularly
a new release about every 2 months
Most releases are documented
notes for 53 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
16 years old
94 releases · first in 2011
Drag across the ruler to compare, or tap a release to open it.
Do not build a held registration's pipeline early by @tillig in #1504 (fixes #1503 ) - a regression introduced in 9.3.3. Registering an open generic f
Do not build a held registration's pipeline early by @tillig in #1504 (fixes #1503) - a regression introduced in 9.3.3. Registering an open generic for several services (.As(typeof(IFirstService<>)).As(typeof(ISecondService<>))) threw InvalidOperationException: Component pipeline has already been built, and cannot be modified. on first resolve whenever anything attached to PipelineBuilding from the component registry's Registered event. Autofac.Extensions.DependencyInjection attaches exactly that way on every registration, so ASP.NET Core applications using a multi-service open generic registration hit it deterministically. The fix restores the ordering 9.3.2 had, where the pipeline is built only after Registered has been raised.
If you are on 9.3.3 and register an open generic against more than one service, upgrade. Thanks to @hjalle for the report and for pinning it to the exact line.
Full Changelog: v9.3.3...v9.3.4
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Create AnyKey adapter registrations per registry by @tillig in #1498 (fixes #1497 ) - the KeyedService.AnyKey fallback adapter was cached and handed t
KeyedService.AnyKey fallback adapter was cached and handed to every registry that asked for it, so the first scope to receive it built and disposed its pipeline out from under the rest. Other scopes then failed to add middleware, resolved through a disposed activator, or adapted another scope's registration. Multitenant containers hit this most often.System.Diagnostics.DiagnosticSource and Microsoft.Bcl.AsyncInterfaces (netstandard2.0 only) move to 10.0.12.Full Changelog: v9.3.2...v9.3.3
Reduce registration cost incurred by scans for [ServiceKey] attribute by @npease18 ( #1495 , fixes #1480 )
Fix per-resolve closure allocation in resolve pipeline ( #1493 ) by @tillig in #1494
Fix per-resolve closure allocation in resolve pipeline (#1493) by @tillig in #1494
Full Changelog: v9.3.0...v9.3.1
Annotate core for trimming and Native AOT compatibility by @tillig in #1492
Full Changelog: v9.2.0...v9.3.0
Fix decorator parameter selection for derived-service dependencies ( #1459 ) by @tillig in #1484
IStartable throws during Build (#1392) by @tillig in #1485ExternallyOwned ownership for decorators (#1402) by @tillig in #1486Module registry events when hooks are overridden (#1446) by @tillig in #1487GetRegistrationId extension to expose a registration's unique ID (#1327) by @tillig in #1490Full Changelog: v9.1.0...v9.2.0
This is a pretty big release for Autofac with some major new functionality!
This is a pretty big release for Autofac with some major new functionality!
First, Autofac now natively supports the concept of AnyKey. It behaves the same way AnyKey works in Microsoft.Extensions.DependencyInjection, but it is native to Autofac directly. The unit tests here show some very detailed examples of usage, but on a high level:
var builder = new ContainerBuilder();
builder.RegisterType<Service>().Keyed<IService>(KeyedService.AnyKey);
var container = builder.Build();
// Registering as AnyKey allows it to respond to... any key!
var service = container.ResolveKeyed<IService>("service1");The new [ServiceKey] attribute allows you to inject the service key provided during resolution. This is handy in conjunction with AnyKey. Again, this is similar to the construct in Microsoft.Extensions.DependencyInjection, but with native Autofac.
First, mark up your class to take the constructor parameter.
public class Service : IService
{
private readonly string _id;
public Service([ServiceKey] string id) => _id = id;
}Then when you resolve the class, the service key will automatically be injected.
You can also make use of this in a lambda registration.
var builder = new ContainerBuilder();
builder.Register<Service>((ctx, p) => {
var key = p.TryGetKeyedServiceKey(out string value) ? value : null;
return new Service(key);
}).Keyed<Service>(KeyedService.AnyKey);Some metrics have been introduced that can allow you to capture counters on how long middleware is taking, how often lock contention occurs, and so on.
Set the AUTOFAC_METRICS environment variable in your process to true or 1 to enable this feature. You can see the set of counters that will become available here.
⚠️ This is NOT FREE. Collecting counters and metrics will incur a performance hit, so it's not something you want to leave on in production.
A pass over the whole system was made with an eye to trying to claw back some performance. Some additional caching was introduced to help reduce lookups and calculations of reflection data; and a few hot-path optimizations were made for the common situations.
Full Changelog: v9.0.0...v9.1.0
Updated Autofac for .NET 10. New current set of target frameworks: net10.0;net8.0;netstandard2.1;netstandard2.0
Updated Autofac for .NET 10. New current set of target frameworks: net10.0;net8.0;netstandard2.1;netstandard2.0
Dropped support for net6.0, net7.0.
net10.0.Full Changelog: v8.4.0...v9.0.0
Minor breaking change : The shim RequiresUnreferencedCodeAttribute has been changed from public to internal ( #1462 / #1463 - thanks @prochnowc !). Th…
Minor breaking change: The shim RequiresUnreferencedCodeAttribute has been changed from public to internal (#1462/#1463 - thanks @prochnowc!). This will only affect people targeting older/lower .NET standard frameworks who also rely on the shim attribute in Autofac. While it's technically breaking, it didn't seem like a great reason to do a full major release due to the edge case nature of the set of applications/users affected.
Corrected nullable markup on IIndex<K,V>.TryGetValue() since it may return null on failure.
IIndex<K,V>.TryGetValue() since it may return null on failure.Full Changelog: v8.2.1...v8.3.0
Fix #1450: AutoActivate() no longer hides the default service registration. (Thanks, @nblumhardt!)
Fix #1450: AutoActivate() no longer hides the default service registration. (Thanks, @nblumhardt!)
Fix #1437: Improve type cache handling for generic type arguments with respect to AssemblyLoadContext disposal (#1438 - thanks @hemirunner426!)
AssemblyLoadContext disposal (#1438 - thanks @hemirunner426!)RegisterServiceMiddleware to assist with interceptors/decorators (#1439 - thanks @idiotsky!)Full Changelog: https://github.com/autofac/Autofac/compare/v8.1.1...v8.2.0
Fix boxing in ResolveRequest.operator==() (#1430, thanks @SergeiPavlov!)
ResolveRequest.operator==() (#1430, thanks @SergeiPavlov!)WithProperty registration methods consistently allow null values (#1428)Full Changelog: https://github.com/autofac/Autofac/compare/v8.1.0...v8.1.1
Optimized required member caching (#1415 - thanks @SergeiPavlov!)
required member caching (#1415 - thanks @SergeiPavlov!)required infrastructure attributes by (#1421 - thanks @DoctorVanGogh!)Full Changelog: https://github.com/autofac/Autofac/compare/v8.0.0...v8.1.0
Removed netcoreapp3.1 support/testing (#1401).
netcoreapp3.1 support/testing (#1401).ResolveRequest into a readonly struct (#1397 - thanks @SergeiPavlov!).net8.0 target (#1401).Full Changelog: https://github.com/autofac/Autofac/compare/v7.1.0...v8.0.0
Fix #1388: Re-enabled RegsiterTypes filtering. This was an accidental behavior regression where the RegisterTypes method wouldn't filter out non-regis
RegsiterTypes filtering. This was an accidental behavior regression where the RegisterTypes method wouldn't filter out non-registerable types.RegisterType<T> and RegisterType(Type t) will now throw when non-registerable types are provided, for example containerBuilder.RegisterType<IInterface>() (you can't register interfaces - you can register things As<IInterface>). This used to throw at container build time; now it throws at RegisterType time and it has a more precise error message so you can handle these issues more proactively.Full Changelog: https://github.com/autofac/Autofac/compare/v7.0.1...v7.1.0
Reduced lock contention in LifetimeScope.CreateSharedInstance (thanks @botinko)
LifetimeScope.CreateSharedInstance (thanks @botinko)Autofac.Features.OpenGenerics.OpenGenericServiceBinder.TryBindOpenGenericTypedService (thanks @SergeiPavlov)Full Changelog: https://github.com/autofac/Autofac/compare/v7.0.0...v7.0.1
Version 7.0.0 is a major increment due to some changes in the target frameworks and some behavioral changes. We summarize these in the documentation,
Version 7.0.0 is a major increment due to some changes in the target frameworks and some behavioral changes. We summarize these in the documentation, but included here as well:
required will now be injected by default. As part of this, the default property injector using PropertiesAutowired() will not inject properties marked required. The documentation has more explanation with examples.AssemblyLoadContext by lifetime scope. A new method, BeginLoadContextLifetimeScope, has been added that allows you to create a lifetime scope tied to a specific AssemblyLoadContext. When the scope is disposed, Autofac will perform a best-effort release of all references to types from that context so the assemblies can be unloaded. The documentation explains this in greater detail.Full Changelog: https://github.com/autofac/Autofac/compare/v6.5.0...v7.0.0
net50 no longer targeted. Autofac will still work with .NET 5 via the netstandard2.1 target, but we recommend you upgrade to a later, supported version of .NET.required will now be injected by default. As noted above, required properties will be injected. This is a behavioral change from Autofac 6.0.required properties. Using PropertiesAutowired() will ignore required properties because it's assumed they must be set during construction rather than post-object-creation.RegisterGeneratedFactory is obsolete. This feature has been replaced by the Func<X, Y, B> built-in relationship and delegate factories.ILifetimeScope has a new BeginLoadContextLifetimeScope method. If you have mocks of ILifetimeScope this method must now be implemented.Reflection caches have moved to a central location Autofac.Core.ReflectionCacheSet (#1341). This is part of an effort to support unloading AssemblyLoa
Autofac.Core.ReflectionCacheSet (#1341). This is part of an effort to support unloading AssemblyLoadContexts associated with child scopes and enable better plugin support (#1324).IDecoratorContext now extends IComponentContext so decorator decisions can be made based on the constructed container (#1338, #1352).Full Changelog: https://github.com/autofac/Autofac/compare/v6.4.0...v6.5.0
That old way _still works and is not deprecated_. You can keep doing that.
WithMetadata and generate metadata (#1299 - thanks @romerod!)IConstructorSelector invocation is skipped (#1325)The new feature to be aware of here is the generic delegates for making lambda registrations easier (#1320, #1321). It makes resolving dependencies in lambdas more straightforward.
The old way meant injecting an IComponentContext and resolving the dependencies manually.
builder.Register(
ctx =>
{
var dep1 = ctx.Resolve<IDependency1>();
var dep2 = ctx.Resolve<IDependency2>();
return new Component(dep1, dep2, "configuration-value");
});
That old way still works and is not deprecated. You can keep doing that.
However, you can now skip the manual resolutions and just provide the dependencies as the parameters to the lambda:
builder.Register(
(IDependency dep1, IDependency dep2) =>
new Component(dep1, dep2, "configuration-value"));
If you need both the context and dependencies for advanced cases, you can do that, too.
builder.Register(
(IComponentContext ctx, IDependency dep1) =>
{
var dep2 = ctx.Resolve<IDependency2>(new NamedParameter("p", "someValue"));
new Component(dep1, dep2, "configuration-value");
});
Modules can now be registered conditionally using an OnlyIf clause. (#1235, #1272)
OnlyIf clause. (#1235, #1272)value to inject by name as that's a reserved word in property setter methods. (#1275)IAsyncDisposable instances that have not been activated are correctly disposed when the scope is disposed. (#1285)TryResolveNamed and TryResolveKeyed. (#1263, #1287 - thanks @v0idzz!)Resolved issues / PRs: - #215: You can now use RegisterAssemblyOpenGenericTypes to do assembly scanning and register open generics! (#1232 / #1246) -
Resolved issues / PRs:
RegisterAssemblyOpenGenericTypes to do assembly scanning and register open generics! (#1232 / #1246)ConfigurePipeline to IComponentRegistration to allow easier registration pipeline modification (related to #1211)ConcurrentBag on different platforms resulted in a memory leak in OnActivated usage; we now flush the ConcurrentBag of registrations on disposal of a lifetime scope (#1257)Added direct support for .NET 5.
ref parameters.…as you expect, you should be aware of the breaking changes and test things out. For the majority case, things should just continue to work; breaking c…
Version 6.0.0 represents a major update in the Autofac internals. While every effort has been made to ensure code using version 5.x will continue to work exactly as you expect, you should be aware of the breaking changes and test things out. For the majority case, things should just continue to work; breaking changes are primarily in more rare advanced usage scenarios.
Check out the release blog post! Also, the documentation has been updated and is ready!
:warning: Starting with Autofac 6.0, we now only target
netstandard20andnetstandard21; we have removed the explicit target fornet461.The impact to you is that, while Autofac will still work on .NET Framework 4.6.1 as it did before, we strongly encourage you to upgrade to .NET Framework 4.7.2 or higher, as per the .NET Standard Documentation, to avoid any of the known dependency issues when using .NET Standard packages in .NET Framework 4.6.1.
There are a lot of new features, but the big ones are here. Other features and fixes will be outlined in the Issues section, below.
DiagnosticSource diagnostics. The core Autofac package ships with a default text-based diagnostic tracer and the new Autofac.Diagnostics.DotGraph package adds graphic tracing using DOT and Graphviz.The following issues have been addressed in v6:
Lazy<T> should now work.Autofac.Diagnostics.DotGraph package.ILifetimeScope.LifetimeScopeEnding event is raised and completes before the scope is disposed.ContainerBuilder is now sealed.DiagnosticSource.Autofac.Pooling package.We'll do our best to keep an upgrade guide with breaking changes available and up to date. We're pretty sure we caught them all, but if you find a gotcha, let us know on the Documentation repo.
A summary of the breaking changes is as follows:
net461 is no longer targeted; Autofac now targets netstandard2.0 and netstandard2.1.log4net module example is shown in the documentation, this now needs to happen through middleware. The log4net module example has been updated to show you the new way it works.RegistrationBuilder.RegistrationData no longer exposes activation handlers. The CoreEventMiddleware is the source of events now.IComponentRegistration no longer exposes activation events. The CoreEventMiddleware is the source of events now.IConstructorSelector implementations need to switch to use BoundConstructor instead of ConstructorParameterBinding.IRegistrationSource implementations need to update the RegistrationsFor method signature.IInstanceActivator implementations no longer have an ActivateInstance method and instead have a ConfigurePipeline method.IComponentRegistry no longer supplies a DecoratorsFor method to check decorators. Use IComponentRegistry.ServiceMiddlewareFor instead.ResolveRequest constructor now takes a ServiceRegistration instead of an IComponentRegistration.ContainerBuilder is now sealed.DiagnosticSource and related entities we (and ASP.NET Core, and others) use for diagnostics is not CLS compliant so Autofac can't be, either.We're working hard to get all of the ~25 integration packages pushed to NuGet as quickly as we can, so please bear with us while we get these sorted.
Some of this is sitting in branches ready to go, other things need to be done now that we have this core package out there.
If your favorite integration isn’t ready yet, we’re doing our best. Rather than filing "When will this be ready?" issues, consider pull requests with the required updates.
Thanks to @VonOgre for a ton of great work on this one.
Fixes:
OnActivating() and OnActivated() should now act more consistently with decorators than it previously did.IEnumerable<T> resolutions.Thanks to @VonOgre for a ton of great work on this one.
#1111 / #1102 - Minor update to handling of provided instances with OnRelease.
#1111 / #1102 - Minor update to handling of provided instances with OnRelease.
Issues resolved: - #1089: Owned instances now allow for async disposal. - #1094: InstancePerOwned now works correctly with keyed registrations. - #109
Issues resolved:
InstancePerOwned now works correctly with keyed registrations.OnRelease called when the container is disposed regardless of whether the instances themselves were resolved from the container.new() generic type constraint should now be correctly handled in open generic registrations.Fix #1085 - StackOverflowException thrown with circular property dependencies
Replaced missing constructor on ResolveRequest to fix accidental break in 5.1.0.
Replaced missing constructor on ResolveRequest to fix accidental break in 5.1.0.
Update NuGet package to use new icon
…4.0 was released in August 2016). There are some breaking changes and new features you should know about as you decide your upgrade strategy.
This is the first major-version release we've had in about three years (Autofac 4.0 was released in August 2016). There are some breaking changes and new features you should know about as you decide your upgrade strategy.
Starting with Autofac 5.0 there is no longer support for .NET 4.5.x. .NET 4.5.2, the last release in that line, follows the same support lifecycle as Windows Server 2012 R2 which ended mainstream support in September 2018.
Autofac 5.0 now targets:
netstandard2.0netstandard2.1net461The container registry can no longer be updated after it has been built.
The ContainerBuilder.Update method was marked obsolete in November 2016 and there has been a robust discussion to answer questions about how to get the container contents to adjust as needed at runtime.
ContainerBuilder.Update has now been removed entirely.
If you need to change registration behavior at runtime, there are several options available to you including the use of lambdas or child lifetime scopes. See this discussion issue for examples and ideas. We will work to add some documentation based on this issue.
Resolving a service from a lifetime scope will now check all parent scopes to make sure none of them have been disposed.
If you dispose a lifetime scope, all children of that lifetime scope will stop resolving objects. In cases like this you'll start getting ObjectDisposedException instead.
If you have a custom application integration that involves creating/destroying lifetime scopes (e.g., custom per-request support) this may cause issues where proper disposal ordering is not occurring.
[Fixes #1020; PR #1061 - thanks @alistairjevans!]
Autofac will no longer do property injection on static properties when auto-wiring of properties is enabled.
If your application behavior depends on static property injection you will need to do some additional work like adding a build callback to populate the property.
[Fixes #1013; PR #1021 - thanks @alistairjevans!]
Autofac lifetime scopes now implement the IAsyncDisposable interface so they can be disposed asynchyronously.
await using (var scope = container.BeginLifetimeScope())
{
var service = scope.Resolve<ServiceThatImplementsIAsyncDisposable>();
// When the scope disposes, any services that implement IAsyncDisposable will be
// Disposed of using DisposeAsync rather than Dispose.
}
[PR #1037 - thanks @alistairjevans!]
Autofac is now build using nullable reference type annotations. This allows developers to get sensible compiler warnings if they opt-in, thus avoiding NullReferenceException instances where possible.
[PR #1037 - thanks @alistairjevans!]
One method of running code at container build time is by registering a build callback. Previously this only worked at the container level, but we've added the ability to register callbacks that run at lifetime scope creation as well.
var scope = container.BeginLifetimeScope(cfg =>
{
cfg.RegisterBuildCallback(scope => { /* do something */ });
});
The callback will be invoked just prior to BeginLifetimeScope exiting, after any startable components are instantiated.
[Fixes #985; PR #1054 - thanks @alistairjevans!]
ParameterFilterAttribute now checks to see if it can resolve a parameter before doing it. (PR #1053 - thanks @RaymondHuy!)IsRegistered no longer throws an IndexOutOfRangeException when called on an open generic type. (PR #1045 - thanks @RaymondHuy!)PropertiesAutowired now works with the new decorator syntax. (PR #1043 - thanks @RaymondHuy!)IsGenericTypeDefinedBy caching for generic type info (PR #1038 - thanks @alistairjevans!)Now that Autofac 5.0 is out, there is still a lot to do. We'll be working on these things as fast as we can:
Some of this is sitting in branches ready to go, other things need to be done now that we have this core package out there.
If your favorite integration isn't ready yet, we're doing our best. Rather than filing "When will this be ready?" issues, consider pull requests with the required updates.
Fix #1006 - Issue with Entity Framework Core DI registrations
Fix #976 - Throw an exception if a lifetime scope is created with a duplicate tag
ComponentNotRegisteredExceptionRegisterAssemblyTypes by putting slow custom attribute check lastReduce the verbosity of activator exception messages; reverts #343.
Fix for #960 - ExternalRegistrySource reuses ExternalComponentRegistration instances causing ObjectDisposedException
ExternalRegistrySource reuses ExternalComponentRegistration instances causing ObjectDisposedExceptionServiceRegistrationInfo.IsInitialized volatile to prevent the ComponentRegistry taking an avoidable lock due to reorderingSwitched from symbol server to SourceLink support
ComponentRegistry to improve concurrency of service resolution (extracted from PR #953)CollectionRegistrationSourceOwned<T>DependencyResolutionException serializableObjectDisposedException on activation if activator is disposedSwitched from symbol server to SourceLink support
Minor performance improvements.
IStartable that creates child lifetime scope during Start() no longer tries to activate itself.Reverted behavior from #897 change to re-include internal and nested private classes for backwards compatibility. Added a new PublicOnly() filter meth
Reverted behavior from #897 change to re-include internal and nested private classes for backwards compatibility. Added a new PublicOnly() filter method to enable opt-in to data encapsulation when scanning for assembly types.
builder.RegisterAssemblyTypes(asm)
.PublicOnly()
.Where(t => t.Name.EndsWith("Repository"))
.Except<MyUnwantedRepository>();
Issues addressed in this release:
Issues addressed in this release:
AutoActivate and IStartable now correctly get run if added to child lifetime scope registrations.AsSelf() and AsImplementedInterfaces() incorrectly ignored custom constructor finders (FindConstructorsWith()).Issues addressed in this release:
Issues addressed in this release:
IStartable and AutoActivate() will be started in dependency order.RegisterType<T>() a type that doesn't have a public constructor.Resolve() operation for a decorated object will pass by the decorators and only be provided to the object being decorated.Resolve() operation will be provided to the constructor selector so they can be used to influence which constructor gets used (IConstructorSelector.SelectConstructorBinding()). This is a minor breaking change for the IConstructorSelector interface but very few people have implemented custom constructor selectors so a major version increment wasn't used.Fix #870: Error building container when class inherits from same generic interface twice.
Fixed #847: ScopeRestrictedRegistry now also applies ComponentRegistrationLifetimeDecorator to registrations from registration sources.
Fixed #730: Added MatchingLifetimeScopeTags() extension to IComponentRegistration to get scope tags.
Added RegisterBuildCallback method to ContainerBuilder that is invoked when the container is built and passed the container instance.
Added conditional registration support (#469). This includes OnlyIf() and IfNotRegistered() registration extensions.
Added conditional registration support (#469). This includes OnlyIf() and IfNotRegistered() registration extensions.
Fixed #816: Generics constrained with generic parameters do not resolve.
Autofac.Extras.AttributedMetadata to core Autofac package making it available in .NET Core.Fixed #807: Improves lifetime scope cleanup for shared instances.
ContainerBuilder.Update obsoleteFor people using ContainerBuilder.Update, we have opened a discussion issue to help you try working around use of Update, explain why we're looking at making it obsolete, and find out where gaps in functionality might be so we can fill those gaps prior to removal.
Fear not, it'll still be around for a while. We just want folks to start looking at fixing things up, or, if it turns out we can't remove Update, find out why it's required so we can address those challenges.
Fixed #495: Improved generic handling in ACTNARS so it no longer interferes with implicit relationship types.
SerializableAttribute polyfill from the Autofac assembly.ContainerBuilder to enable sharing of data across component and module registrations.Fixed #728: AnyConcreteTypeNotAlreadyRegisteredSource now ignores string parameters.
Fixed #789: Property injection was incorrectly considering parameters during resolution. InjectProperties now allows parameters to be passed if that f
Fixed #789: Property injection was incorrectly considering parameters during resolution. InjectProperties now allows parameters to be passed if that functionality is required.
Updated minimum specific .NET framework target to be .NET 4.5.
uap10.0 framework target since it's covered by netstandard1.1.New target platform set `netstandard1.1`. This includes support for .NET Core and UWP (Universal Windows Platform). You can read more about the new ne
netstandard1.1. This includes support for .NET Core and UWP (Universal Windows Platform). You can read more about the new netstandard target framework monikers and the associated compatibility on the .NET Core documentation.Microsoft.Extensions.DependencyInjection abstraction. This can be found in the Autofac.Extensions.DependencyInjection NuGet package.PreserveExistingDefaults option now works correctly across lifetime scopes when registrations are added during the creation of a child lifetime scope.IPropertySelector to choose which properties should be property injected.AsImplementedInterfaces now includes the actual interface being registered preventing the need to call AsSelf as well.Serializable attribute so that .NET 4.5.1 consumers can serialize DependencyResolutionException across AppDomain etc. as was possible prior to migrating to PCL.DependencyResolutionException is thrown if an InstancePerLifetimeScope service attempts to create an instance of itself during its construction.AsClosedTypesOf that accepts a serviceKey or serviceKeyMapping for keyed registrations.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.