rikvandenberg / azurefunctions.extensions.dependencyinjection

An Microsoft.Extensions.DependencyInjection based implementation based on CJ van der Smissen Azure Function Autofac Dependency Injection

Dependency Injection in Azure Functions using Microsoft.Extensions.DependencyInjection

A Microsoft.Extensions.DependencyInjection implementation based on the Autofac based implmenetation of CJ van der Smissen AzureFunctions.AutoFac

AzureFunctions.AutoFac on NuGet

AzureFunctions.Extensions.DependencyInjection on NuGet

Usage

In order to implement the dependency injection you have to create a class to configure DependencyInjection and add an attribute on your function class.

Configuration

Create a class and call the DependencyInjection.Initialize method. Perform the registrations as you normally would with Autofac.

public class Startup
{
    public Startup()
    {
        if(!DependencyInjection.IsInitialized)
        {
            DependencyInjection.Initialize(ConfigureServices);

            // Some other stuff such as AutoMapper.
            Mapper.Initialize(c =>
            {
                AzureFunctionsAutoMapperConfig.Initialize(c);
                BusinessAutoMapperConfig.Initialize(c);
            });
        }            
    }

    public static void ConfigureServices(IServiceCollection services)
    {
        services.AddSingleton<IQueryDispatcher, QueryDispatcher>();
        services.AddBusinessLayer();
    }
}

Function Attribute and Inject Attribute

Once you have created your Startup or 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 IServiceCollection in order for this to work.

[ConfigureServices(typeof(Startup))]
public class GreeterFunction
{
    [FunctionName("GreeterFunction")]
    public static HttpResponseMessage Run([HttpTrigger(AuthorizationLevel.Function, "get", Route = null)]HttpRequestMessage request, 
        TraceWriter log, 
        [Inject]IGreeter greeter, 
        [Inject]IGoodbyer goodbye)
    {
        log.Info("C# HTTP trigger function processed a request.");
        return request.CreateResponse(HttpStatusCode.OK, $"{greeter.Greet()} {goodbye.Goodbye()}");
    }
}

Using Named Dependencies [Unsupported]

Support has been added to use named dependencies. Simple add a name parameter to the Inject attribute to specify which instance to use.

[ConfigureServices(typeof(Startup))]
public class GreeterFunction
{
    [FunctionName("GreeterFunction")]
    public static HttpResponseMessage Run([HttpTrigger(AuthorizationLevel.Function, "get", Route = null)]HttpRequestMessage request, 
        TraceWriter log, 
        [Inject]IGreeter greeter, 
        [Inject("Main")]IGoodbyer goodbye, // Unsupported
        [Inject("Secondary")]IGoodbyer alternateGoodbye // Unsupported
    )
    {
        log.Info("C# HTTP trigger function processed a request.");
        return request.CreateResponse(HttpStatusCode.OK, $"{greeter.Greet()} {goodbye.Goodbye()} or {alternateGoodbye.Goodbye()}");
    }
}

azurefunctions.extensions.dependencyinjection's Issues

Update to latest versions of WebJobs packages

Hi. Do you think you could update to the latest WebJobs packages so that this is compatible with Microsoft.Net.Sdk.Functions 1.0.13?

Is there any example to use this DI for injecting EF Core DbContext

This is my startup class, and I cannot get the Azure function registered if I try to inject the context to my function.

public class Startup
{
    public Startup()
    {
        if (!DependencyInjection.IsInitialized)
        {
            DependencyInjection.Initialize(ConfigureServices);
        }
    }

    public static void ConfigureServices(IServiceCollection services)
    {
        var config = new ConfigurationBuilder()
            .SetBasePath(Environment.CurrentDirectory)
            .AddJsonFile("local.settings.json", optional: true, reloadOnChange: true)
            .AddEnvironmentVariables()
            .Build();

        var connectionString = config.GetConnectionString("SqlConnectionString");
        services.AddDbContext<_MyContext>(options => options.UseSqlServer(connectionString));
    }
}

License

This seems like it could be useful to a lot of people, but there isn't a license included, which I think means it defaults to not being usable (although by github's terms I think we could fork it and use the fork).

Could you add a license of some kind, please?