Updated Autofac reference to 9.3.1.

Breaking Changes

• Updated the Autofac dependency from 8.0.0 to 9.2.0.
• Updated Microsoft.Extensions.Configuration dependencies from 8.x to 10.0.9:
  • Microsoft.Extensions.Configuration
  • Microsoft.Extensions.Configuration.Binder

What's Changed

• Added explicit support for net8.0 and net10.0 target frameworks; continued support for netstandard2.0 and netstandard2.1.
• Fixed empty JSON array handling with Microsoft.Extensions.Configuration 10.x so empty arrays continue to behave compatibly with previous configuration behavior.

Full Changelog: v7.0.0...v8.0.0

Breaking Changes

• Updated minimum core Autofac to 8.0.0, which minor breaking changes and target framework updates. See release notes for core Autofac.
• Updated minimum Microsoft.Extensions.Configuration to 8.0.0. Previously specifying empty arrays and objects in configuration would have those values seen as null. With this update, empty arrays and objects in configuration are seen instead as empty.

Additional Changes

• Modules specified in configuration will now attempt to use the constructor that matches the set of configured parameters and will fall back to the constructor with the most parameters (#44 / #45 - thanks @pnagoorkar!)
• Added nullable type annotations.

Full Changelog: v6.0.0...v7.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.

Resolve #8: Added support for complex type parameters and properties in module configuration.

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.

• Dropped net45 and netstandard1.3 support - new target frameworks are net461 and netstandard2.0.
• Fix #26: Type conversion from string value to strong type (e.g., string to double) now uses invariant culture to allow better portability of configuration agnostic of machine culture. This appears to primarily affect users of XML format configuration since JSON has better support for types (e.g., numbers, Booleans), but there is no guarantee that JSON is totally unaffected.

• #18: Now throwing a more informative exception when XML configuration is malformed.
• Added SourceLink support.
• Added netstandard2.0 target.

Updated to target .NET 4.5 for larger compatibility with Autofac core.

• Switched from using XML configuration to using Microsoft.Extensions.Configuration - enables XML, JSON, or other configuration formats supported by that package.
• Targeting netstandard 1.3 and .NET 4.5.1.

This release occurred prior to switching Autofac components to separate repositories.

3.3.0

• Added an AppSettingsModule to enable configuration of module parameters using appSettings.
• Resolved issue autofac/Autofac#546: Added auto-activate attribute on components to enable auto activation via config.

3.2.0

• Resolved issue autofac/Autofac#445: Added property and parameter support for specifying a [Type Converter] attribute that will be used during parsing of configuration.

3.1.0

• First release of separate NuGet package for XML based configuration.