If you're new to Autofac, the Quick Start guide is a good place to start. There's also an official documentation site, API documentation, and lots of info on the Autofac wiki.

Welcome to Autofac’s documentation! Autofac is an addictive IoC container for .NET. It manages the dependencies between classes so that applications stay easy to change as they grow in …

The sample app gives you an idea of how to use Autofac, but there’s a lot more you can do. Check out the list of integration libraries to see how to integrate Autofac with your application.

From Autofac 7.0 onwards, for reflection components, all required properties are automatically resolved at the time of object construction, and are generally treated in much the same way as …

If you are unable to use the Autofac interfaces and you need per-request or instance-per-dependency services in your filters, you must use service location. Luckily, Web API makes …

In your Startup class (which is basically the same across all the versions of ASP.NET Core) you then use ConfigureContainer to access the Autofac container builder and register things …

If you aren’t writing a .NET Core app that requires it or if you’re not using any of the DI extensions provided by other libraries you can consume Autofac directly. You also may only need to do …

The metadata feature of Autofac provides a KeyFilterAttribute that allows you to mark constructor parameters with an attribute specifying which keyed service should be used.

Example In Autofac, modules implement the Autofac.Core.IModule interface. Generally they will derive from the Autofac.Module abstract class. This module provides the IVehicle service:

When you resolve your component, Autofac will see that you have an ILogger registered, but you don’t have an IConfigReader registered. In that case, the second constructor will be chosen …