ArnaudB88

@alastairtree Can you please take a look at the pull request? Thanks! Edit: the code in pull request #91 does not work for me. I currently use the following (as...

@alastairtree Can you please review the open pull request, and if ok complete it? The pull request is based on your first method (from the docs) to empty the entire...

Does not work correctly in my project (working with dependency injection)

The dependency injection code should also be changed. More specific in: - LazyCache/LazyCache.AspNetCore/LazyCacheServiceCollectionExtensions.cs - LazyCache/LazyCache.Ninject/LazyCacheModule.cs How should it be changed? There are 2 options: Option A: work with a cacheProvider...

> > > @ArnaudB88 Does the new injection code look ok? Looks fine to me. But it's good to let it review by someone else than me. I have experience...

@alastairtree This pull request is basically your first method to empty the entire cache. In my opinion, a clean and more easy to understand way than method 2. It just...

My pull request was closed for the reason that the library should not depend on System.Web and because the solution was not 100% safe. https://github.com/alastairtree/LazyCache/pull/111#issuecomment-607703593 Following suggested solution does not...

@alastairtree Can you please take a look at my suggestions above? Thanks!

As you can see in my original post, that is not an option: > That method uses other classes which are instantiated with dependency injection. Instances of that class are...

I added a unit test project illustrating the behavior I am trying to explain: https://github.com/ArnaudB88/LazyCache/tree/Bug_110 See the project LazyCache.UnittestsAspNet. The cached method should be executed in the current HttpContext since...