Peter Kellner
MVP ASP.NET

I’ve started to use your EFProviderWrapper in a Windows Service application. The app creates WCF interfaces, and a cliens can ask, and send data to the app. When a client send something, i write it to the database, and there is a method when i can ask back the stored values.
My problem is, that after i insert a new value (with LINQ), it appears in the database, but when i try to query it with a LINQ expression, is gives back the cached data, but without the newly inserted value.
Do you have any idea, why i can’t get back the new value, just after restarting my application?

Thank you!

Regards!

Thank you

I found 2 possible bugs in the EF Wrapper 1.02.

1. From time to time I am getting an exception on this line from the EntityConnectionWrapperUtils:
var storeConnection = DbProviderFactories.GetFactory(ecsb.Provider).CreateConnection();

Exception:
System.Web.HttpUnhandledException (0×80004005): Exception of type ‘System.Web.HttpUnhandledException’ was thrown. —> System.ArgumentException: An item with the same key has already been added.
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at EFProviderWrapperToolkit.EntityConnectionWrapperUtils.CreateEntityConnectionWithWrappers(String entityConnectionString, String[] wrapperProviders) in C:\Users\Bruno\Downloads\EF4ProviderWrappers\EF4ProviderWrappers\EFProviderWrapperToolkit\EntityConnectionWrapperUtils.cs:line 58

2. The InMemoryCache, unlike AspNetCache, doesnt do a Hash on the key before adding it to the cache, so big SQL are not being added to the cache. My idea would be use MemoryCache from 4.0, or hash the sql before adding it to the cache.

Please, let me know if you need further explanation.

Thanks

Thanks much.

Am I missing something or is that capability not implemented?

Thanks

Hi Jarek,

I have a quick question for you.
I just recently started digging in to EF 4.0 and needed some logging/tracing capabilities. I came across EFTracingProvider witch looks great but unfortunately not working for me.

My question is therefore: is it still needed to use EFTracingProvider for tracing or have I missed some built in feature of EF 4.0 that does the same?

Thanks and regards,
Ronny

I have a quick question for you.
I just recently started digging in to EF 4.0 and needed some logging/tracing capabilities. I came across EFTracingProvider witch looks great but unfortunately not working for me.

My question is therefore: is it still needed to use EFTracingProvider for tracing or have I missed some built in feature of EF 4.0 that does the same?

Thanks and regards,
Ronny

I found the EFProviderWrappers project yesterday and have been testing it with AppFabric Caching (Velocity) as a Cache-Through provider. One thing I noticed was with ambient transactions via TransactionScope, Cache.InvalidateSets() never gets called.

It appears that the underlying SQLConnection is enlisting in the ambient transaction, however the DBConnectionWrapper.EnlistTransaction never gets called.

After some digging, I think I have come up with a solution to the problem. However I haven’t ever touched this part of the framework before and I am curious if this is the proper way to solve the problem.

You can see the gist of my code additions at https://gist.github.com/797390

Basically in EFCachingConnection.Open, I enlist in the ambient transaction using a custom IEnlistmentNotification (EFCachingEnlistment) that does the same thing as the EFCachingTransaction.

The EFCachingCommand updates the CachingEnlistment when one exists on the EFCachingConnection… the same way it would if the EFCachingTransaction existed.

Thanks in advance, and feel free to use this code to add the functionality to the EFCachingProvider. Also if I am doing something completely wrong, please let me know.

Thanks,
Scott Beardsley