Skip to content

Releases: autofac/Autofac.Extras.Moq

v7.0.0

01 Oct 18:10
1dd73a7
Compare
Choose a tag to compare

⚠️ LOOKING FOR AN OWNER! This package is largely in maintenance mode - if you'd like to help the community out and pull it out of maintenance mode, come drop us a line!

This is primarily a dependency and framework update. It is the first release where the library is effectively in maintenance mode. Check out the pinned issue here for more about what this means and what you can do to help.

  • Breaking changes:
  • Other changes:
    • Update all dependencies as possible. Includes update to Moq 4.18.4.
    • Update nullable type annotations.
    • Fix invalid test that incorrectly registered an abstract class.

Full Changelog: v6.1.1...v7.0.0

v6.1.1

26 Jul 16:47
Compare
Choose a tag to compare

Fix for #43: Setup for AutoMock.Mock<T> should now be obeyed in child lifetime scopes. (PR #46 - thanks, @xzxzxc !)

v6.1.0

21 Oct 15:22
Compare
Choose a tag to compare

#44 - Added overloads for Create<T>() that allow providing a type as a parameter. (Thanks @kdriedger!)

v6.0.0

02 Oct 07:55
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.

In addition, this release contains a fix for issue #35, resolving some problems with strict mocks and disposable components. Thanks @JarkoDubbeldam for the contribution!

v5.0.1

22 Mar 21:54
6290a95
Compare
Choose a tag to compare

#33 - Ensure that the correct exception is thrown if no zero-parameter constructor is present
#31 - Apply the appropriate type filtering so that value types can be used as service constructor parameters.

v5.0.0

25 Feb 21:15
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.

Breaking Change Note:
In this release, the Provide method on the AutoMock has been removed because it is now not compatible with Autofac's immutable container. Check the docs for guidance on how to provide custom dependencies following this change.

Changes:

  • No longer targeting net45 or netstandard1.3
  • Now targeting net461, netstandard2.0, and netstandard2.1.
  • Fix #21 - Decorators should work as expected.
  • Fix #22 - ComponentNotRegisteredException issue resolved by new Autofac.
  • Fix #25 - IEnumerable<T> mocking issue fixed.

v4.3.0

23 Oct 20:56
Compare
Choose a tag to compare
  • #15: Checking auto-mock concrete types to ensure there is a zero-parameter constructor so Castle.DynamicProxy and MockRepository.Create<T> can correctly work on concrete types under the covers.
  • #17: Meta<T> now interpreted correctly by Autofac instead of being mocked.
  • #20: Callback for modifying the container before auto-mocking takes over.
  • Updated minimum Autofac version to 4.2.0 for an improved new project experience.
  • Added netstandard2.0 specific target to improve dependency chain on newer projects.

v4.2.0

02 Oct 15:17
Compare
Choose a tag to compare

Fix #3: No longer allowing mocks of Lazy<T> or Owned<T> to enable support for Autofac built-in relationships.

v4.1.0

28 Sep 16:03
Compare
Choose a tag to compare
  • Support for netstandard1.3.
  • Updated to Moq 4.7.0.

v4.0.0

03 Jan 21:14
Compare
Choose a tag to compare
  • Updated to .NET 4.5 support.
  • Enabled Autofac 4.0 support.