12 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Simon de Kraa commented  ·  October 13, 2012 5:31 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Especially on Windows Azure where at the moment you have quite a performance penalty using SQL Azure and with the availability of Windows Azure cache to me this seems like a must have on Windows Azure.

• useroger33 commented  ·  August 13, 2012 2:33 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Also a sample with dbcontext http://www.codeproject.com/Articles/435142/Entity-Framework-Second-Level-Caching-with-DbConte

• Vahid Nasiri commented  ·  June 25, 2012 8:59 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Here you can find an implementation of second level caching in EF Code first:
  http://www.dotnettips.info/File/UserFile?name=EfSecondLevelCaching.zip

• Alexandre commented  ·  January 24, 2012 5:49 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  This is already something that can be acheived http://msdn.microsoft.com/en-us/magazine/hh394143.aspx but it should be something simple to accomplish.

• bchoi commented  ·  September 14, 2011 11:34 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  @Tommy compare EFCachingProvider to NHibernate's built in configurable option. 2nd level cache is a must for ORM and should be readily available to the user.

• Tommy commented  ·  March 11, 2011 6:59 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Unless I don't understand this issue correctly, this would be achieved by simply expanding upon Jaroslaw Kowalski's example of implementing first level caching:
  http://blogs.msdn.com/b/jkowalski/archive/2009/06/11/tracing-and-caching-in-entity-framework-available-on-msdn-code-gallery.aspx

  His example already provides access to the underlying connections and commands, which you should have no problem using to extend as described?

• Byung Choi commented  ·  February 9, 2011 11:53 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  EF should be easily extensible. One of the main concern is caching.
  Hibernate and NHibernate went through this issue years ago.

• Felipe Fujiy Pessoto commented  ·  January 6, 2011 2:15 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Cache isn´t responsability of domain.
  Cache is a cross-cutting concern.

• henrik commented  ·  January 5, 2011 11:59 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  ASP really need cashing support.

• Bassam commented  ·  September 15, 2010 1:37 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  if that means the ability to query the datacontext offline without db connection using LINQ , then that would be really cool and much much needed

• Denis Kotov commented  ·  September 14, 2010 1:21 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Caching is needed for ASP.NET applications. Possibility addition dependence on changes in a source by SqlCacheDependency.

• Unai Zorrilla commented  ·  September 13, 2010 10:21 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Nooooooooooooooo, cache is responsability of domain, cache is bussines no data .......