#585 AutoCrossWireAspNetComponents overload added that accepts IServiceProvider.This information was already available in. NET Standard 2.0 version now includes the stack trace that caused the container to either be locked or disposed. #369 In case Simple Injector throws an exception explaining that the container is either locked or disposed, the.Any collection, registered using Collection.Register can now be injected and resolved as either a List or Collection. #545 List and Collection dependencies are now supported out of the box.#559 NuGet package now contains a.NET Standard 2.0 version.support for List and Collection dependencies.NET Standard 2.0 version of the Simple Injector core library, which limits the number of installed NuGet packages on machines There is a new SimpleInjectorPageModelActivatorProvider that can be registered and a container.RegisterPageModels(app) extension method that can be used to register Razor Page Models. #572 Added ASP.NET 2.0 Razor Page support to the ASP.NET Core MVC integration package.#648 Added information about lifestyles to when the container visualized object graph (both inside the VS debugger and when calling VisualizeObjectGraph).The addition of ASP.NET Core 2.0 Razor Page integration.The introduction of a ContainerScope that allows access to the singleton Scope.The prevention of iteration of injected collections inside constructors of Singleton consumers.#540 Removed the use of ThreadLocal from the decorator sub system, which could cause memory leaks in case the user didn't dispose the container.#671 Prevented WebRequestLifestyle from reusing the same Scope instance over multiple containers inside the same web request.#603 New Collection.Append and Collection.AppendInstance overloads added that simplify appending registrations (and instances) to collections.#664 New Container.ContainerScope property allows access to the container-global Scope, which can be used to register objects for disposal and execute delegates when the container is disposed, while allowing to retrieve created disposables, which enables async dispose.Special thanks to our new contributor for implementing this. #377 switch introduced that allows disabling resolving unregistered concrete types.You can use the Container.IsVerifying property instead. #670 AdvancedExtensions.IsVerifying(Container) extension method was made obsolete.A suppression can be added in case the warning is a false positive.
#554 Iterating collections with scoped or transient dependencies inside a singleton consumer now causes an exception when resolved or verified to prevent captive dependencies/lifestyle mismatches.The package contains a new SimpleInjectorPageModelActivatorProvider class that can be added to ASP.NET's IServiceCollection and a container.RegisterPageModels(app) extension method that can be used to register Razor Page Models. The addition of integration for ASP.NET Core 2.0 Razor Pages.This prevents supprises in the future, as we are changing the default behavior to false in v5.0. Users are advised to change the setting to false. The introduction of an Options.ResolveUnregisteredConcreteTypes switch that allows disabling resolving unregistered concrete types.The introduction of a Container.ContainerScope property that allows access to the singleton Scope.The diagnostics will warn when injected injected collections are iterated/used inside constructors of singleton consumers.ServiceCollection Integration packages #639 #683 Prevented double disposing cross-wired dependencies.#689 Common System.Object methods ( ToString, GetHashCode, Equals, and GetType) are now hidden from common API classes when using IntelliSense.#681 Extra information added to obsolete messages.#706 Added the ability to ignore disposing scoped and singleton components.#691 Added (Type, Type, Lifestyle) overload.#685 VisualizeObjectGraph can now generate fully qualified type names.#701 SimpleInjector.Scope default ctor marked obsolete.#699 ExpressionBuiltEventArgs ctor marked obsolete.Ability to visualize object graphs with fully qualified type names.Read the documentation here and here for more details. New integration packages for non-ASP.NET Core environments that still require IServiceCollection, such as.Please read the documentation for more details. New fluent configuration model for ASP.NET Core that aims to simplify integration.The most prominent improvements in this release are:
0 kommentar(er)
