Releases: autofac/Autofac.Extras.AggregateService
Releases · autofac/Autofac.Extras.AggregateService
v6.1.2
What's Changed
- Resolve #11: Use Func<X, Y> to handle methods with parameters by @tillig in #12 - Aggregate service methods with open generic parameters now correctly use the parameters during resolution. Note that, due to the complexity of working with open generic arguments, the type matching/factory is delegated to core Autofac and will result in two resolution operations per call - one to resolve a
Func<X, Y>
based on the method parameter types (with closed generics); one to execute thatFunc<X, Y>
to resolve the actual object.
Full Changelog: v6.1.1...v6.1.2
v6.1.1
v6.1.0
v6.0.0
This is a compatibility release for Autofac 6.0.
Breaking change: Starting with Autofac 6.0, we now only target netstandard2.0
and netstandard2.1
; we have removed the explicit target for net461
. While this package was only targeting netstandard2.0
before, upgrading to this version will bring in Autofac v6 and the associated TFM change for that transitive dependency.
v5.0.0
This release is an update for compatibility with Autofac 5.0.0 and requires that new version. Autofac 5.0.0 does have some breaking changes - see the Autofac release notes for more information.
- Target
netstandard2.0
- Minimum Autofac 5.0.
v4.1.0
Added support for netstandard 1.3 via Castle.Core 4.0.0.
v4.0.0
v3.0.4
This release occurred prior to switching Autofac components to separate repositories.
3.0.4
- Minor NuGet packaging fixes.
3.0.3
- Resolved issue autofac/Autofac#476: Updated Castle.Core reference to 3.2.2 for all consuming packages. A critical bug fix was made available for Dynamic Proxy.
3.0.2
- Castle version was not updated to 3.2.0 in previous release due to build script issue.
3.0.1
- Resolved Issue autofac/Autofac#409: Updated Castle references to 3.2.0.