Skip to content

Releases: autofac/Autofac.Configuration

v7.0.0

13 Jul 21:15
4fff3f5
Compare
Choose a tag to compare

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

v6.0.0

28 Sep 20:37
Compare
Choose a tag to compare

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.1.0

19 Feb 17:28
Compare
Choose a tag to compare

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

v5.0.0

30 Jan 01:30
Compare
Choose a tag to compare

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.

v4.1.0

21 Jun 16:17
Compare
Choose a tag to compare
  • #18: Now throwing a more informative exception when XML configuration is malformed.
  • Added SourceLink support.
  • Added netstandard2.0 target.

v4.0.1

03 Nov 16:28
Compare
Choose a tag to compare

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

v4.0.0

03 Nov 16:16
Compare
Choose a tag to compare
  • 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.

v3.3.0

03 Nov 16:27
Compare
Choose a tag to compare

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.