This is my 2nd iteration of the code. Because MemoryCache is thread safe you don’t need to lock on the initial read, you can just read and if the cache returns null then do the lock check to see if you need to create the string. It greatly simplifies the code. const string CacheKey = … Read more
As per the documentation, you have a few options here: If your filters have dependencies that you need to access from DI, there are several supported approaches. You can apply your filter to a class or action method using one of the following: ServiceFilterAttribute TypeFilterAttribute IFilterFactory implemented on your attribute ServiceFilter or TypeFilter attributes If … Read more
Wow, so I just spent entirely too much time digging around in the CLR with reflector, but I think I finally have a good handle on what’s going on here. The settings are being read in correctly, but there seems to be a deep-seated problem in the CLR itself that looks like it will render … Read more
So, here’s some news. We looked into this and YES, this is a bug in .NET 4. The good news is that it was fixed in .NET 4.5, so if you can, update your installation to .NET 4.5 and you’re solid. The other good news it that this fix has been back-ported to .NET 4 … Read more
Dispose the existing MemoryCache and create a new MemoryCache object.