|
|
Hi, When looking for my manifest resources, ParseResources() (EntityConnecti onWrapperUtils. cs, line 186) throws a NotSupportedExc eption : "The invoked member is not supported in a dynamic assembly". This is due to this assembly: "Anonymously Hosted DynamicMethods Assembly, Version=0.0.0.0 , Culture=neutral , PublicKeyToken= null", which is a dynamic assembly. Before calling "GetManifestRes ourceStream" (that throws the exception), you exclude Ecma and System assemblies. I suggest you should exclude Dynamic assemblies too : EntityConnectio nWrapperUtils.c s, line 184 : foreach (Assembly asm in assembliesToCon sider.Where(asm => !IsEcmaAssembly (asm) && !IsSystemAssemb ly(asm) && !asm.IsDynamic) ) Please, let me know what you think about this. Thank you for your great toolkit ! Claire
I don't know if this will help you but I was getting a "dynamic library exception" and after a bit of searching I found that the "*" in the EF database connection string can be a cause. It suggested that you replace the 3 occurrences of "*" with the name of the DLL (without the .dll) that contains your EF code. Cured my issue.
I notice the current download no longer has support for AppFabric caching. In the readme it says "6. Removed Velocity adapter and the demo." However, the project description still shows using VelocityCache. Can you clarify? Are you adding back in or keeping it out?
Hi, I'm also trying to use AppFabric cache. Can you tell me if you succeeded in using it ? Thank you, Claire
I cannot get the EFTracingProvider to work when calling CreateDatabase( ). I get the following error: The provider manifest given is not of type 'System.Data.Sq lClient.SqlProv iderManifest'.
I tried looking for some way to contribute but could not find anything on the site. I found one defect in the code which occurs when loading the wrapper if there are dynamically generated libraries included in the current AppDomain. In that circumstance EntityConnectionWrapperUtils will throw a NotSupportedExc eption on line 186 (method ParseResources when calling asm.GetManifest ResourceStream( resourceName)). Fix: just wrap the using call to asm.GetManifest ResourceStream( resourceName) in a try/catch block filtering on exception NotSupportedExc eption. Again, thank you for your efforts in providing the community with a good wrapper for the Entity Framework.
Igor, I'm curious to know in what scenario you get this error. I haven't encountered it yet and want to be prepared! :) THanks.
Thank you for the wrapper, I have found it very useful. I do have one request with the update of your page, could you post the version information again so we can see when something has changed and what has changed? I believe you provided this on the last page which was most useful.