search

tieonlinux / ZygorDownloader

Always up to date Zygor guides
https://tieonlinux.github.io/ZygorDownloader/
7 stars 1 forks source link

Bump SimpleInjector from 5.1.0 to 5.3.0 #14

Closed dependabot[bot] closed 3 years ago

dependabot[bot] commented 3 years ago

Bumps SimpleInjector from 5.1.0 to 5.3.0.

Release notes

Sourced from SimpleInjector's releases.

Simple Injector v5.3

This release is available through Nuget.

When upgrading from v4.x, please make sure you upgrade your application to the latest v4.x version of Simple Injector first. After that upgrade directly to the latest v5.3.x release.

This minor release contains the following improvements and new features:

  • #897 Added a new convenient Container.GetTypesToRegister<T>(IEnumerable<Assembly>, TypesToRegisterOptions) overload.
  • #891 Container.GetRegistration<T>() failed with cast exception. This generic overload was added in v5.0, but almost never worked.
  • #863 Loosened up locking behavior of GetRegistration. A call to GetRegistration is now much less likely to cause the container to be locked. Thanks to @​AroglDarthu for suggesting this.
  • #880 Allowed an existing Scope to be provided to a ScopedLifestyle to allow it to become the current active ambient scope. This feature was especially added for corner-case scenarios, such as Blazor integration.
  • #812 Improved exception messages caused by type initialization. TypeInitializationExcpetions, thrown by the .NET Framework are annoying and not very useful. When such exception is thrown while Simple Injector is resolving a type, Simple Injector will now transform the failure in a much more readable error message.
  • #864 Improved the message of the Disposable-Transient-Component diagnostic warning. Thanks to @​AroglDarthu for suggesting this.

Simple Injector v5.2.1

This release is available through Nuget.

When upgrading from v4.x, please make sure you upgrade your application to the latest v4.x version of Simple Injector first. After that upgrade directly to the latest v5.2.x release.

This patch fixes a concurrency bug that was introduced in v5.2.0 and impacts users of all builds except .NET Standard 2.1. All v5.2.0 users are advised to upgrade to this patch release.

  • #883 Intermittently receiving IndexOutOfBoundsException from AsyncDisposableTypeCache.IsAsyncDisposable in 5.2.0

Simple Injector v5.2

This release is available through Nuget.

WARNING: There was a multi-threading bug introduced in this release that could impact most users. Please skip this release and upgrade to (at least) v5.2.1.

When upgrading from v4.x, please make sure you upgrade your application to the latest v4.x version of Simple Injector first. After that upgrade directly to the latest v5.2.x release.

This minor release implements the following work items:

  • #873 Verification fails with IAsyncDisposable registrations
  • #867 Prevent Microsoft.Bcl.AsyncInterfaces dependency

The most important change in this minor release is #867, which solves the binding redirect issues that users have reported since the introduction of v5. This is done by removing the Microsoft.Bcl.AsyncInterfaces NuGet package dependency (#867). Unfortunately, this forces the following breaking changes in the core library:

  • [BREAKING] The Scope.RegisterForDisposal(IAsyncDisposable) method is removed and replaced with a Scope.RegisterForDisposal(object) overload.
  • [BREAKING] In the .NET Standard 2.0 and .NET 4.6.1 builds of Simple Injector, Container and Scope no longer implement IAsyncDisposable effectively removing Container.DisposeAsyc() and Scope.DisposeAsync() from those builds.

These breaking changes were required because the removal of the Microsoft.Bcl.AsyncInterfaces dependency disallows Simple Injector types to implement IAsyncDisposable. Fortunately, unless you were calling DisposeAsync yourself, an upgrade to Simple Injector v5.2 is likely a graceful one. For a more detailed discussion on what the problem was, please read our blog post.

The problem was urgent enough to force these breaking changes on a minor release, instead of making this into a major release, which takes much more planning and time.

NOTE: Do note that if you are using ASP.NET Core, you must upgrade the ASP.NET Core integration packages as well. The old packages will break with v5.2.

This doesn't mean, though, that asynchronous disposal isn't possible anymore. On the contrary actually. Where previous minor releases only allowed asynchronous disposal in the .NET 4.6.1, .NET Standard 2.0, and .NET Standard 2.1 builds of Simple Injector, asynchronous disposal is now supported in all builds. To make this possible, the following additions have been made:

  • The pre-.NET Standard 2.1 builds of Simple Injector apply duck typing internally to recognize types that implement IAsyncDisposable. This means that Simple Injector checks if your type implements an interface named "System.IAsyncDisposable". Upon disposal, Simple Injector expects that interface to contain an DisposeAsync method. That method should either return Task, or ValueTask. This means that you can either let your application depend on Microsoft.Bcl.AsyncInterfaces or define the interface yourself. As always, we ensured maximum performance; even this duck typing is blazingly fast.
  • The .NET Standard 2.1 build of Simple Injector skips duck typing and simply expects a asynchronous disposable type to implement the official IAsyncDisposable. .NET Standard 2.1 (which means you're either running .NET Core 3 or .NET 5) is provided out of the box.

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 3 years ago

Superseded by #19.