Improved MemoryCache Usage

[Tornhoof]

The first example of using the MemoryCache creates an extra MemoryCacheEntryOptions object,just to set the sliding expiry time. Unfortunately this example is a bit misleading, because it is unclear if MemoryCacheEntryOptions can be reused as it is not marked thread-safe. The bottom line is, that this being the first example, it will lead to developers creating that object just to set extra values even though there are better options available (as you know, everyone just looks for the first copyable code piece ;)). I will create a PR which adds a code sample with Set and absolute expiry without the MemoryCacheEntryOptions in it. Imho it would be better to change the first example, not to use sliding but this would require rather large changes to the narrative of this page or just use the CreateEntry api, but that api is way too clunky to be used in normal circumstances.

This is a direct result of dotnet/runtime#45436

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 13f5f8f9-18dd-9c12-9ed1-fcc6b44ba7fd
• Version Independent ID: 640b4f36-5886-7b69-1c95-cfc8574a02fd
• Content: Cache in-memory in ASP.NET Core
• Content Source: aspnetcore/performance/caching/memory.md
• Product: aspnet-core
• Technology: aspnetcore-performance
• GitHub Login: @Rick-Anderson
• Microsoft Alias: riande