LazyCache
LazyCache copied to clipboard
An easy to use thread safe in-memory caching service with a simple developer friendly API for c#
**Describe the bug** If I have (directly or indirectly) already registered an `IMemoryCache` instance with the DI container, then `services.AddLazyCache()` fails with the following exception: > System.Security.VerificationException: Method Microsoft.Extensions.DependencyInjection.ServiceDescriptor.Singleton: type...
Hello, **thank you for sharing your great work!** **Describe the bug** 'bug' is the best matching issue type because the doc in Wiki is very useful, but it has still...
Fixes: #130 Changes: * Adds XML documentation fo: IAppCache, CachingService and DI extension methods
[Use the Thumbs Up reaction to vote for this feature, and please avoid adding comments like "+1" as they create noise for others watching the issue.] **Is your feature request...
[Use the Thumbs Up reaction to vote for this feature, and please avoid adding comments like "+1" as they create noise for others watching the issue.] **Is your feature request...
Disposing and then creating a new cache is problematic at times. Having a `Clear()` method resolves that. I think adding `ICacheProvider.Clear()` is the best way to do this. But here...
I suggest the following code instead: ```cs public static bool ExTryGetValue(this IAppCache service, string key, out T? value) where T : class { var item = service.Get(key); if (item is...
Not to denigrate LazyCache as it's been incredibly useful up to now. But going forward, is there any reason to continue with LazyCache instead of using the new HybridCache? thanks...
[Use the Thumbs Up reaction to vote for this feature, and please avoid adding comments like "+1" as they create noise for others watching the issue.] **Is your feature request...
**Describe the bug** Creating two separate instances of LazyCache, using default constructor will share the same underlying memory. I'm not sure if this is a bug or by design, but...