Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 564
  • Last Modified:

Why place EF model in seperate project

I'm struggling to figure out how to set up my Visual Studio 2010 c# based solution.  I want to create a library to used by both a web application and windows application.  The solution will store data in a SQL Server db via Entity Framework 4.0.

It seems common practice to put the model in a seperate library but how much application logic to add to this?  For example I am downloading data from Paypal so am saving Paypal transactions in the DB.  So in my core library do I have a PaypalSystem (what I communicate with to retrieve the transactions) and put PaypalTransaction in the Model library?  It seems a muddle to me and I think I could use advice or an example!
0
canuckconsulting
Asked:
canuckconsulting
1 Solution
 
Carl TawnSystems and Integration DeveloperCommented:
If the database to which the EF model maps is shared by multiple applications then it would make sense to move it into a separate library. If not then I don't really see the point since the EF model maps to a particular schema, so is fairly tightly tied to the application that uses it.

Putting your PayPal stuff into it's own library might make sense. That way you make it reusable across applications and you could still make it use your existing EF model if that too was in a separate library. At least then you would have option of more easily detaching the PayPal stuff from the database if you wanted to.  
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now