Table of Contents

Ploch.Common.DependencyInjection.Autofac

Autofac container integration for the ServicesBundle pattern. This package is currently a stub. The Autofac project file (Plocch.Common.DependencyInjection.Autofac.csproj — note the typo in the filename) references Ploch.Common.DependencyInjection and Autofac.Extensions.DependencyInjection but contains no additional source files beyond the project definition. The usage examples below are aspirational/planned and are not based on existing source code. Check the repository for the current state before depending on this package in production.

Overview

Ploch.Common.DependencyInjection.Autofac bridges the ServicesBundle pattern from Ploch.Common.DependencyInjection with the Autofac IoC container via Autofac.Extensions.DependencyInjection.

When your application uses Autofac as its DI container (typically registered via UseServiceProviderFactory(new AutofacServiceProviderFactory())), this package enables the same AddServicesBundle call pattern to work against Autofac's ContainerBuilder / IServiceCollection bridge rather than the bare Microsoft DI container.

Installation

Note: The project file is named Plocch.Common.DependencyInjection.Autofac.csproj (with a typo — Plocch instead of Ploch). Since no <PackageId> is set, the NuGet package ID inherits this misspelling. Until the project is renamed or a PackageId override is added, the actual install command would use the misspelled name. Given that this package is currently a stub, this is not yet actionable.

Key Types

This package re-exports the full ServicesBundle API from Ploch.Common.DependencyInjection and provides Autofac-compatible registration support through the Autofac.Extensions.DependencyInjection bridge.

Type Source Description
IServicesBundle Ploch.Common.DependencyInjection Core bundle interface
ServicesBundle Ploch.Common.DependencyInjection Base class for bundles
ConfigurableServicesBundle Ploch.Common.DependencyInjection Configuration-aware base class
AutofacServiceProviderFactory Autofac.Extensions.DependencyInjection Registers Autofac as the service provider factory

Usage Examples

Generic Host with Autofac and ServicesBundle

Register Autofac as the container factory in the Generic Host, then use bundles as normal:

var host = Host.CreateDefaultBuilder(args)
    .UseServiceProviderFactory(new AutofacServiceProviderFactory())
    .ConfigureServices((context, services) =>
    {
        services.AddServicesBundle<ApplicationBundle>(context.Configuration);
        services.AddServicesBundle<InfrastructureBundle>(context.Configuration);
    })
    .Build();

Bundles are written identically to the standard ServicesBundle pattern — the Autofac package handles the container wiring transparently.

ASP.NET Core with Autofac

builder.Host.UseServiceProviderFactory(new AutofacServiceProviderFactory());

builder.Services.AddServicesBundle<WebApiBundle>(builder.Configuration);

Configuration

No additional configuration beyond the standard ServicesBundle pattern. Ensure Autofac is registered as the service provider factory before calling AddServicesBundle.

Edit this page