v5.5

These packages are available through Nuget. Please see the integration guide on how to use these integration packages.

This minor release contains no functional changes nor bug fixes. This release changes how packages are referenced in the NuGet package:

• #37 Large number of dependencies when installing SimpleInjector.Integration.AspNetCore.Mvc.Core

v5.4

These packages are available through Nuget. Please see the integration guide on how to use these integration packages.

This minor release adds several small improvements:

• #32 Allow multiple Simple Injector containers, coupled to a single service collection, to be disposed on shutdown
• #33 Allow Controllers, ViewComponents, PageModels, and TagHelpers to be resolved with Flowing scopes

v5.3

These packages are available through Nuget. Please see the integration guide on how to use these integration packages.

This minor release adds several small improvements:

SimpleInjector.Integration.ServiceCollection

• #14 Allowed replacing the IServiceScope by adding a new ServiceScopeProvider class. This gives easier integration with Blazor and Azure Functions.
• #15 Added an SimpleInjectorAddOptions.EnableHostedServiceResolution flag that allows disabling resolution of hosted services for easier integration with Azure Function, which not supports hosted services.
• #18 Added a public SimpleInjectorAddOptions.ServiceScopeFactory to simplify accessing MS.DI's IServiceScopeFactory as this service isn't resolvable through cross-wiring.
• #17 .AddSimpleInjector now registers MS.DI's IServiceScope before calling the setupAction; this gives greater freedom to anyone who wants to replace it.

SimpleInjector.Integration.AspNetCore

• #11 Added a SimpleInjectorAddOptions Options property to SimpleInjectorAspNetCoreBuilder to give access to SimpleInjectorAddOptions from inside extension methods that are built upon SimpleInjectorAspNetCoreBuilder.
• #5 Removed the where TMiddleware : IMiddleware generic type constraint from the UseMiddleware<TMiddleware>() extension method to prevent C# overload resolution from accidentally calling UseMiddlewareExtensions.UseMiddleware<T>(IApplicationBuilder, object[]) which leads to really confusing error messages.

SimpleInjector.Integration.AspNetCore.Mvc.Core

• #8 Added AddControllerActivation overload that accepts a Lifestyle. This simplifies registering controllers with an alternative lifestyle.

v5.2

These packages are available through Nuget. Please see the integration guide on how to use these integration packages.

This minor release solves binding redirect issues that multiple users have reported over the last months. This is done by removing the Microsoft.Bcl.AsyncInterfaces NuGet package dependency from the core library and the ASP.NET Core integration packages (#7).

WARNING: These packages now require at least ASP.NET Core 2.1.

This update contains no new functionality nor bug fixes. You should upgrade to v5.2 when you upgraded the core library to v5.2 or when you are experiencing binding redirect issues, but even users without these issues are advised to upgrade, because binding redirect issues can easily emerge in the future when your application starts to depend on other (completely unrelated) NuGet packages.

For a more detailed discussion on what the problem was, please read our blog post.

v5.1.1

The packages are available through Nuget. Please see the integration guide on how to use these integration packages.

This patch release consists solely of an update of the ASP.NET Core integration NuGet packages and their dependencies. These packages now refer to the Simple Injector v5.1 core library and SimpleInjector.Integration.ServiceCollection v5.0.2. Especially the ServiceCollection integration package contains an important update for ASP.NET Core users, which would otherwise not be downloaded by NuGet.

SimpleInjector.Integration.ServiceCollection v5.0.2

This package is available through Nuget.

This patch release fixes three bugs:

• #4 Registration of Singletons implementing IAsyncDisposable caused exception on shutdown when options.DisposeContainerWithServiceProvider is set to true (the default)

v5.1

New features:

• #3 Added AddAspNetCore overload that allows overriding the IServiceScope reuse behavior. Example:

  services.AddSimpleInjector(options =>
  {
      options.AddAspNetCore(ServiceScopeReuseBehavior.OnePerNestedScope);
  });

v5.0

Release Notes

The Simple Injector v5 integration packages are available through Nuget. For more background information about this release and a general overview, please read the blog post.

Before you upgrade to v5.0, please make sure you upgrade your application to the latest 4.x version of Simple Injector first.

Overview

Breaking changes

Below you find the complete list of all the breaking changes in the core library and all officially supported integration libraries.

ASP.NET Core Integration

• #587 AspNetCore.Mvc.Core integration package is split into two separate packages. ViewFeature-related stuff (i.e. the AddViewComponentActivation() extension method) is moved to SimpleInjector.Integration.AspNetCore.Mvc.ViewFeatures, while controller integration (i.e. AddControllerActivation()) is still in SimpleInjector.Integration.AspNetCore.Mvc.Core. This allows integrating Simple Injector with a ASP.NET Core Web API project without pulling all framework assemblies that are related to view feature related stuff (such as MVC views, view components, etc). You will be affected when your application depends directly on SimpleInjector.Integration.AspNetCore.Mvc.Core while calling AddViewComponentActivation().
• #809 Several obsoleted methods and classes have been removed. To prevent any problems, make sure you upgrade to the latest v4.x release first before upgrading to v5. Only upgrade to v5 after fixing all compiler warnings and errors

API Difs

• SimpleInjector.Integration.ServiceCollection
• SimpleInjector.Integration.AspNetCore.Mvc.Core
• SimpleInjector.Integration.AspNetCore.Mvc