Releases: autofac/Autofac.Mef
v7.0.0
Breaking Changes
Updated minimum core Autofac to 8.0.0, which includes similar target support updates. See release notes for core Autofac.
What's Changed
- Updated System.ComponentModel.Composition to 8.0.0.
- Added support for
net8.0
,net7.0
, andnet6.0
to match both Autofac 8 and System.ComponentModel.Composition 8.
Full Changelog: v6.1.0...v7.0.0
v6.1.0
What's Changed
Fix #1: Resolving Lazy<T, TMetadata>
should now work. (Thanks @holdenmai!)
Full Changelog: v6.0.1...v6.1.0
v6.0.1
v6.0.0
Version 6.0.0 is a compatibility release for Autofac v6.
Breaking change: Starting with Autofac 6.0, we now only target netstandard2.0
and netstandard2.1
; we have removed the explicit target for net461
.
The impact to you is that, while Autofac will still work on .NET Framework 4.6.1 as it did before, we strongly encourage you to upgrade to .NET Framework 4.7.2 or higher, as per the .NET Standard Documentation, to avoid any of the known dependency issues when using .NET Standard packages in .NET Framework 4.6.1.
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.
v4.1.0
v4.0.0
v3.0.3
This release occurred prior to switching Autofac components to separate repositories.
3.0.2
- Resolved issue autofac/Autofac#348: MEF exports always set their prerequisite imports during resolution.
- Switched fix for autofac/Autofac#348: Instead of always setting export prerequisites, setting the appropriate lifetime scope sharing on exports fixes the problem in a cleaner fashion.
3.0.1
Bug Fixes
- Issue autofac/Autofac#425: MEF integration crash when attempting to map exports to services when no matching type identity is found.