Multiple Projects in a solution - Entity Framework and ASP.Net MVC 4

Question

For a school project I am building an application that has to be splitted in multiple projects.

The projects that will be made are class libraries, a wcf service and a asp.net MVC4 application.

The class libraries will be a state library, a stateless library and a datalogic library.

Ideally entity framework should be in the datalogic library, the generated models should be placed in the state library and the classes in stateless contain static methods to save those models.

However I can't seem to get the models generated by Entity Framework (v5) to another class library (State). Is there some way to do this? Or do I think wrong, should I use another architecture?

This problem is solved: Entity Framework 5 and Visual Studio 2012 POCO Classes in Different Project

Advice on architecture is still welcome:

I am willing to change this structure, if mine is proven wrong or less efficient as the one adviced.

(Other information I may need to provide is that the WCF service will pass through the methods of the stateless library and the ASP.Net MVC4 application is using those methods to get the models and some controller functionality)

Are you adding references to the various projects as necessary? — Kenneth K.
– Kenneth K., Commented Mar 6, 2013 at 19:19
We do a similar thing to this but use CodeFirst EF not db/modelfirst — undefined
– undefined, Commented Mar 6, 2013 at 19:19
Are you using the EF DbContext POCO Generator? It's then reasonably straight forward to have the .edmx context and poco models in different assemblies - msdn.microsoft.com/en-US/data/jj206878 — Neil Thompson
– Neil Thompson, Commented Mar 6, 2013 at 19:35
having a database already doesnt prevent you using codefirst. Personally i handstich POCO classes based on the database and use the modelbuilder if i want to represent it differently in the model. However you can also use the CodeFirst Generator to produce a codefirst model from an existing db. — undefined
– undefined, Commented Mar 6, 2013 at 19:46
Using database first, or code first, is a matter of preference and isn't really the issue here IMO. Using POCOs should make it easy to separate the models and context as @NeilThompson suggested — EdmundYeung99
– EdmundYeung99, Commented Mar 6, 2013 at 19:51

Community · Accepted Answer · 2017-05-23 12:14:31Z

4

(So you can mark an answer)

Are you using the EF DbContext POCO Generator?

It's then reasonably straight forward to have the .edmx context and poco models in different assemblies - msdn.microsoft.com/en-US/data/jj206878 –

As you discovered - this post on Entity Framework 5 and Visual Studio 2012 POCO Classes in Different Project explains the procedure well.

Julie Lerman also has downloadable solutions from her books & courses that show POCo T4 templates and lots of other good practices

edited May 23, 2017 at 12:14

CommunityBot

11 silver badge

answered Mar 6, 2013 at 20:33

Neil Thompson

6,4652 gold badges33 silver badges55 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Multiple Projects in a solution - Entity Framework and ASP.Net MVC 4

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related