Updated Autofac reference to 9.3.1.

Breaking Changes

• Dropped support for .NET 6 and .NET 7. These target frameworks have been removed. Projects targeting net6.0 or net7.0 must move to a supported framework.
• Updated the minimum Autofac dependency to 9.3.0 (from 8.0.0). This is a major-version upgrade of Autofac and will be applied transitively to consumers.

Other Changes

• Added support for .NET 10 and .NET Standard 2.1; retained support for .NET 8 and .NET Standard 2.0.
• Updated System.ComponentModel.Composition to 10.0.9.

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, and net6.0 to match both Autofac 8 and System.ComponentModel.Composition 8.

Full Changelog: v6.1.0...v7.0.0

What's Changed

Fix #1: Resolving Lazy<T, TMetadata> should now work. (Thanks @holdenmai!)

Full Changelog: v6.0.1...v6.1.0

Fix #23: MEF registration sources should no longer create duplicate dependency resolutions when used with a lifetime scope and registration action.

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.

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.

• Update to .NET Standard 2.0 using System.ComponentModel.Composition NuGet package

• Updated to .NET 4.5.
• Verified Autofac 4.0 compatibility.

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.