An Autofac based implementation of Dependency Injection based on Boris Wilhelm's azure-function-dependency-injection and Scott Holden's WebJobs.ContextResolver available on NuGet as AzureFunctions.Autofac
- Supports utilizing Autofac within Azure Functions
- Supports lifetime scoping
- Supports named dependency resolution
- Supports post container build actions for additonal configuration
- Supports injection of
ILogger<>derived from providedILoggerFactoryfor clean logging - Supports container caching for speed and memory efficiency with the ability to disable if required
- Supports verification of dependency injection configs through unit testing extesions
In order to implement the dependency injection you have to create a class to configure DependencyInjection and add an attribute on your function class.
The configuration class is used to setup dependency injestion. Within the constructor of the class DependencyInjection.Initialize must be invoked. Registrations are then according to standard Autofac procedures.
In both .NET Framework and .NET Core a required functionName parameter is automatically injected for you but you must specify it as a constructor parameter. You can also use the optional ILoggerFactory parameter, to register it into the container, and therefore allow Autofac to inject ILogger<> into your services.
In .NET Core you have another optional baseDirectory parameter that can be used for loading external app configs. If you wish to use this functionality then you must specify this as a constructor parameter and it will be injected for you.
public class DIConfig
{
public DIConfig(string functionName)
{
DependencyInjection.Initialize(builder =>
{
//Implicity registration
builder.RegisterType<Sample>().As<ISample>();
//Explicit registration
builder.Register<Example>(c => new Example(c.Resolve<ISample>())).As<IExample>();
//Registration by autofac module
builder.RegisterModule(new TestModule());
//Named Instances are supported
builder.RegisterType<Thing1>().Named<IThing>("OptionA");
builder.RegisterType<Thing2>().Named<IThing>("OptionB");
}, functionName);
}
} public class DIConfig
{
public DIConfig(string functionName, string baseDirectory, ILoggerFactory factory)
{
DependencyInjection.Initialize(builder =>
{
//Implicity registration
builder.RegisterType<Sample>().As<ISample>();
//Explicit registration
builder.Register<Example>(c => new Example(c.Resolve<ISample>())).As<IExample>();
//Registration by autofac module
builder.RegisterModule(new TestModule());
//Named Instances are supported
builder.RegisterType<Thing1>().Named<IThing>("OptionA");
builder.RegisterType<Thing2>().Named<IThing>("OptionB");
// Configure Autofac to provide ILogger<> into constructors
builder.RegisterLoggerFactory(factory);
}, functionName);
}
}Once you have created your config class you need to annotate your function class indicating which config to use and annotate any parameters that are being injected. Note: All injected parameters must be registered with the autofac container in your resolver in order for this to work.
[DependencyInjectionConfig(typeof(DIConfig))]
public class GreeterFunction
{
[FunctionName("GreeterFunction")]
public static HttpResponseMessage Run([HttpTrigger(AuthorizationLevel.Function, "get", Route = null)]HttpRequestMessage request,
ILogger log,
[Inject]IGreeter greeter,
[Inject]IGoodbyer goodbye)
{
log.LogInformation("C# HTTP trigger function processed a request.");
return request.CreateResponse(HttpStatusCode.OK, $"{greeter.Greet()} {goodbye.Goodbye()}");
}
}An extra attribute, ScopeFilterAttribute, is necessary for Functions V1 to properly release the objects created by the autofac container.
[DependencyInjectionConfig(typeof(DIConfig))]
[ScopeFilter]
public class GreeterFunction
{
[FunctionName("GreeterFunction")]
public static HttpResponseMessage Run([HttpTrigger(AuthorizationLevel.Function, "get", Route = null)]HttpRequestMessage request,
ILogger log,
[Inject]IGreeter greeter,
[Inject]IGoodbyer goodbye)
{
log.LogInformation("C# HTTP trigger function processed a request.");
return request.CreateResponse(HttpStatusCode.OK, $"{greeter.Greet()} {goodbye.Goodbye()}");
}
}With Azure Functions v2 it is now possible to provide an optional ILoggerFactory when setting up the Dependency Injection Config.
You will need to add a using statement in the Dependency Injection Config for AzureFunctions.Autofac.Shared.Extensions and add the following line in your Initialize function:
builder.RegisterLoggerFactory(factory);It will now be possible for Autofac to inject into your classes an ILogger<> that can be used to output to the console or configured location.
An example of this is in the Microsoft Docs as well as in this repo in the LogWriter
Note that you must also update the host.json file to contain a Logging Configuration. See the Microsoft Docs for more details.
Support has been added to use named dependencies. Simple add a name parameter to the Inject attribute to specify which instance to use.
[DependencyInjectionConfig(typeof(DIConfig))]
public class GreeterFunction
{
[FunctionName("GreeterFunction")]
public static HttpResponseMessage Run([HttpTrigger(AuthorizationLevel.Function, "get", Route = null)]HttpRequestMessage request,
ILogger log,
[Inject]IGreeter greeter,
[Inject("Main")]IGoodbyer goodbye,
[Inject("Secondary")]IGoodbyer alternateGoodbye)
{
log.LogInformation("C# HTTP trigger function processed a request.");
return request.CreateResponse(HttpStatusCode.OK, $"{greeter.Greet()} {goodbye.Goodbye()} or {alternateGoodbye.Goodbye()}");
}
}In some cases you may wish to have different dependency injection configs for different classes. This is supported by simply annotating the other class with a different dependency injection config.
[DependencyInjectionConfig(typeof(DIConfig))]
public class GreeterFunction
{
[FunctionName("GreeterFunction")]
public static HttpResponseMessage Run([HttpTrigger(AuthorizationLevel.Function, "get", Route = null)]HttpRequestMessage request,
ILogger log,
[Inject]IGreeter greeter,
[Inject]IGoodbyer goodbye)
{
log.LogInformation("C# HTTP trigger function processed a request.");
return request.CreateResponse(HttpStatusCode.OK, $"{greeter.Greet()} {goodbye.Goodbye()}");
}
}
[DependencyInjectionConfig(typeof(SecondaryConfig))]
public class SecondaryGreeterFunction
{
[FunctionName("SecondaryGreeterFunction")]
public static HttpResponseMessage Run([HttpTrigger(AuthorizationLevel.Function, "get", Route = null)]HttpRequestMessage request,
ILogger log,
[Inject]IGreeter greeter,
[Inject]IGoodbyer goodbye)
{
log.LogInformation("C# HTTP trigger function processed a request.");
return request.CreateResponse(HttpStatusCode.OK, $"{greeter.Greet()} {goodbye.Goodbye()}");
}
}If you wish to perform actions on the DI container after it has been built you can pass an Action<IContainer> as the last parameter of the DependencyInjection.Initialize function.
public class DIConfig
{
public DIConfig(string functionName)
{
var tracer = new DotDiagnosticTracer();
tracer.OperationCompleted += (sender, args) =>
{
// Writing the DOT trace to a file will let you render
// it to a graph with Graphviz later, but this is
// NOT A GOOD COPY/PASTE EXAMPLE. You'll want to do
// things in an async fashion with good error handling.
var path = Path.Combine(Path.GetTempPath(), $"{Guid.NewGuid()}.dot");
using var file = new StreamWriter(path);
file.WriteLine(args.TraceContent);
};
DependencyInjection.Initialize(builder =>
{
builder.RegisterType<Greeter>().As<IGreeter>();
}, functionName, c => c.SubscribeToDiagnostics(tracer));
}
}By default containers are cached using the function name and a new lifetime scope of the container is created for each function invocation. This means that if you register a type as single instance then it will be provided to each function with the same name even though they are in different lifetime scopes. In some cases this behavior is not desired and as such you can disable caching during dependency injection initialization by passing enableCaching as false
public class DIConfig
{
public DIConfig(string functionName, string baseDirectory, ILoggerFactory factory)
{
DependencyInjection.Initialize(builder =>
{
builder.RegisterType<Sample>().As<ISample>().SingleInstance();
}, functionName, enableCaching: false);
}
}Dependency injection is a great tool for creating unit tests. But with manual configuration of the dependency injection, there is a risk of mis-configuration that will not show up in unit tests. For this purpose, there is the DependencyInjection.VerifyConfiguration method.
It is not recommended to call VerifyConfiguration unless done so in a test-scenario.
VerifyConfiguration verifies the following rules:
- That an
InjectAttributeis preceeded by aDependencyInjectionConfigAttribute. - That the configuration can be instantiated.
- That all injected dependencies in the given type can be resolved with the defined configuration.
- Optionally that no redundant configurations exist, i.e. a
DependencyInjectionConfigAttributewith no correspondingInjectAttribute.
Below is a very simple example of verifying the dependency injection configuration for a specific class:
DependencyInjection.VerifyConfiguration(typeof(MyCustomClassThatUsesDependencyInjection));If you don't want to verify rule 4, pass in false as the second parameter to VerifyConfiguration:
DependencyInjection.VerifyConfiguration(typeof(MyCustomClassThatUsesDependencyInjection), false);For instance, you can use it in a unit test to verify that all classes in your project has dependency injection set up correctly:
[TestMethod]
public void TestDependencyInjectionConfigurationInAssembly() {
var assembly = typeof(SomeClassInYouProject).Assembly;
var types = assembly.GetTypes();
foreach (var type in types) {
DependencyInjection.VerifyConfiguration(type);
}
}I love programming and all but as both a day job and a hobby it can get tiring. I mean I could have just been drinking a beer or playing some games. If this project helped you advance your own work then why not consider buying me a beer...
and I will raise one to you! Much appreciated!