Question

We have two web applications and each one is creating it’s own data context for EF. When I make changes to an entity in one app I see the changes on the page and in the database when I view the data in SQL Server Mangement Studio. However, I don’t immediately see the changes in the other application.

Both apps use dependency injection and both applications use the same business layer and data layer. So the UI in both apps go through a common controller class (not to be confused with MVC controllers) and the controller goes through the repository for the entity it is retrieving. Because they are different apps they each have their own instance of entity framework data context.

If there is some kind of caching, how might I turn that off?

Thanks in advance.

EDIT – Maybe the caching is ocurring somewhere above EF? Clearing my browser cache doesn’t seem to fix the issue. After some time goes by I will suddenly see the update to the record in the other app, but for a while no amount of refreshing will show me the updates.

Answer 1

If the caching is occurring in the context, the cached values should go away when you dispose of the context at the end of the current HTTP request. You do have a per-request context, right?

Here’s some context lifetime best practices.