Caching provider: TransactionScope does not invalidate cache?

Oct 6, 2013 at 9:00 PM
Edited Oct 6, 2013 at 9:13 PM

I see great value in the project and I am very grateful for your time to build and share this code, but after reviewing this I see one significant problems that prohibit me from using in any production environment.

There is no support for ambient transactions. If you wrap your DbContext.SaveChanges inside a transactionscope the EfCachingConnection fails to invalidate the cache. I found a Github Gist for this which was sent to Jarek Kowalski in 2011 but unfortunately the bug remains an issue to this day. I have seen examples of wrapping transactionscopes or altering their code for transactions to compensate for this bug, I believe the gist fixes it directly.

I had a SECOND bug claiming that I could not find support for aspnetcache, but I found this in a separate DLL, so there is only one issue.