All Versions
107
Latest Version
Avg Release Cycle
40 days
Latest Release
1001 days ago
Changelog History
Page 6
Changelog History
Page 6
-
v4.7.0 Changes
February 22, 2017Minor change only (correcting Moq version after semver violation) This version is the successor of 4.6.62-alpha.
-
v4.6.62-alpha Changes
February 21, 2017🔀 This version is the predecessor of 4.7.0 and essentially a cleaned up merge of both 4.5.30 and 4.6.39-alpha.
Note: The release notes for some Moq versions 4.6.*-alpha are still missing. They need to be reconstructed from the commit history and the GitHub issue archive. If you would like to help make this changelog more complete, any pull requests towards that goal are appreciated!
-
v4.5.30 Changes
January 09, 2017🛠Fixed
- 🛠Fix issue in
ExpressionKey
that caused identical setups to no longer be considered the same (@MatKubicki, #313)
- 🛠Fix issue in
-
v4.5.29 Changes
December 10, 2016🛠Fixed
- 👉 Make the recently added
setup.ReturnsAsync(Func<TResult> result)
evaluate its argument lazily, likesetup.Returns
would (@SaroTasciyan, #309)
- 👉 Make the recently added
-
v4.5.28 Changes
November 11, 2016âž• Added
- 🆕 New method
setup.ReturnsAsync(Func<TResult> result)
(@joeenzminger, @tlycken, #297)
- 🆕 New method
-
v4.5.23 Changes
October 11, 2016🛠Fixed
- 👌 Improves comparison of call arguments in
ExpressionKey
so that setups for the same method but with differing arguments don't override each other (@MatKubicki, #291)
- 👌 Improves comparison of call arguments in
-
v4.5.22 Changes
September 20, 2016🛠Fixed
- 🤡 Properly raise events when mocked type implements multiple interfaces (@bradreimer, #288)
-
v4.5.21 Changes
August 12, 2016🛠Fixed
- 🛠Fix
mock.Reset()
which so far forgot to also clear all existing calls in the interceptor (@anilkamath87, #277)
- 🛠Fix
-
v4.5.20 Changes
August 12, 2016🛠Fixed
- 🤡 Ensure that mocking of
System.Object
methods always works, even in strict mode (again) (@kolomanschaft, #280)
- 🤡 Ensure that mocking of
-
v4.5.19 Changes
August 10, 2016🛠Fixed
- 🤡 Make
SetupAllProperties
work withDefaultValue.Mock
in the presence of object graph loops (i.e. when a type contains a property having the same type) (@vladonemo, #245) - 🤡 Prevent invalid implementations of
ISerializable
from being mocked (as DynamicProxy cannot handle these) via the newSerializableTypesValueProvider
decorator (@vladonemo, #245)
- 🤡 Make