v2.0.0

2.0.0 keeps every public type, member and parameter name of 1.0.1 and answers every call as 1.0.1 did on .NET Framework, with the exceptions listed under Fixed: tests/Golden holds 158 calls recorded from the published 1.0.1, and the golden test replays them against every build on .NET Framework 4.8 and .NET 10. Cache keys are 1.0.1's: byte for byte on .NET Framework, and on .NET apart from the last digit of a small share of doubles and floats (.NET formats the 17th digit exactly where the Framework rounded it); every value still has one key. The major version is for the dependencies: the API names Autofac and Castle.Core types, whose majors move.

Changed

• Targets netstandard2.0 and net10.0 (1.0.1: net45). Runs on .NET Framework 4.6.2+, .NET 8 and .NET 10; 1.0.1 could not create a proxy on any .NET Core runtime (Castle.Core 3.2.2 needs System.Security.Permissions).
• Depends on Autofac.Extras.DynamicProxy 7.1.0 or later (replacing Autofac.Extras.DynamicProxy2 3.0.5), Autofac 6.5.0 or later, Castle.Core 5.1.1 or later and System.Runtime.Caching 10.0.12. Works with Autofac 6.5 to 9.
• Cache keys are written by a built-in JavaScriptSerializer-compatible writer (System.Web.Extensions exists only on .NET Framework).
• Package icon, README, Source Link, symbols package, deterministic build.

Fixed

• A [Cache] method that returns null ran on every call and then threw ArgumentNullException at the caller; the null is now returned and cached.
• A [Cache] void method threw ArgumentNullException after running; void methods now run and are not cached.
• MemoryCacheService.Get(key, func) threw ArgumentNullException when func returned null, and ran it again next time; the null is now returned and cached.
• MemoryCacheService.Get(key, func) returned the default without running func when the key held a value of another type; it now runs func and replaces the value.
• new MemoryCacheService(ObjectCache) gave every entry a lifetime of zero, so it kept nothing; it now uses the five-minute default.
• A lifetime too large for a date (long.MaxValue ticks, TimeSpan.MaxValue) threw ArgumentOutOfRangeException after the intercepted method ran; it now never expires. One too small for a date keeps nothing, like any negative lifetime.
• The per-key lock table was an unsynchronised static Dictionary that grew with every key, and intercepted calls took no lock: concurrent callers all ran the method. Concurrent calls with one key now run it once, and the table only holds keys being computed.
• A [Cache] method returning a Task kept a faulted or cancelled task forever; such tasks are now removed. Methods returning ValueTask are not cached (a ValueTask may be awaited only once).
• An argument that cannot be written into a key (a reference cycle, nesting deeper than 100, a dictionary with non-string keys, an enum based on long or ulong, a key over the length limit) made the call throw before the method ran; the call now runs uncached. DefaultCacheKeyService.GenerateUniqueKeyForCall itself still throws, as in 1.0.1. An exception thrown by the argument itself while its key is built (an iterator, a getter) still reaches the caller.

Removed

• The .NET Framework 4.5 project files, the nuspec, and the nupkgs that were committed in the repository.

v2.0.0-beta.1

The release rehearsal of 2.0.0: the same code and notes as the 2.0.0 section below, published as a prerelease to prove the release path (Trusted Publishing, the approval gate, verification from nuget.org).