Print Page | Close Window

Entityframwork with Devforce object model

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce 2010
Forum Discription: For .NET 4.0
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=1813
Printed Date: 21-Apr-2026 at 10:39am


Topic: Entityframwork with Devforce object model
Posted By: amit007
Subject: Entityframwork with Devforce object model
Date Posted: 14-May-2010 at 12:28pm
We have a project that has reference to both Devforce object model and Entity Framework object model, but when we run the project, devforce object model throws exception type "ReflectionTypeLoadException". If we remove the Entity Framework object model reference from the project, it works fine. We have verified the edmx file names and the both are named different. Does anyone know if there is an additional setting needs to be set or missing? We have setup this project setup just exactly as the sample project except it has Entity Framework reference.
 
Thanks,
Amit


Replies:
Posted By: ting
Date Posted: 14-May-2010 at 8:45pm

We have confirmed this as a bug.  Thanks for pointing this out.

Until this gets fixed, you will need to keep the raw Enity Framework EDMX in a different project from the DevForce-enhanced EDMX.  Probably not a bad idea anyway if they're two different models.
 

Posted By: amit007
Date Posted: 17-May-2010 at 6:36am
Both of these models were created in separate library project and then added as reference, but problem still persist. If I remove the entity framework project reference, then as expected dev force object model works.

Posted By: ting
Date Posted: 17-May-2010 at 5:24pm

Thanks for the additional information.  This is probably an issue with probing by MEF (Managed Extensibility Framework).  We're taking a look at it now.

Posted By: DapperDanH
Date Posted: 18-May-2010 at 8:40am
Thanks for verifying what we are seeing.  Any estimate of when this could be addressed?   This is a brick wall for us and preventing us from moving forward.
 
Thoughts?
 
Dan Hickman
ProModel Corporation.

Posted By: kimj
Date Posted: 18-May-2010 at 2:13pm
We're not able to reproduce the problem if the models are in separate assemblies.  Can you provide some more information on the solution structure?

Posted By: amit007
Date Posted: 19-May-2010 at 11:36am

The structure is pretty simple. We are not doing anything out of the ordinary. Entity Framework assembly project was created with .net 3.5 and we had used this for creating dev force object model with previous version. Once it was converted over to 4.0, we created separate assembly project for dev force object model. But if we reference both of these assemblies project, dev force object model ends of throwing "ReflectionTypeLoadException".  Hopefully this helps.


Thanks,
Amit

Posted By: kimj
Date Posted: 19-May-2010 at 3:28pm
I'm sorry Amit but that doesn't help, as we already understand that you have one class library holding the EF model and another class library holding the DevForce model, and that referencing both assemblies causes the error.   We are unable to reproduce the behavior you're seeing, in other words, it's working for us.  Since we can't repro, we have to assume that something else is going on.  If you'd like, you can send us a sample solution showing the problem.


Print Page | Close Window