Geek Answers Handbook

Create an N-Tier Unbundled Application with Entity Framework and VB.NET

So, we are creating an application with

  • UI Layer (website, mobile, Ajax client, etc.)
  • Service Level / API
  • Business logic level
  • Data access level

Our goal is to make Entity Framework dependent on service level to DAL. This means that the Sevice layer will accept and return POCO (plain old CLR objects).

Currently, we are manually encoding the mapping layer between the service level and the business logic level, which converts POCO to EF objects and vice versa.

So, in short, the page has a form, the form has a codebehind that takes the contents of the form, fills them in POCO and sends it to the service level. The service level is converted to EF Entity, sends it to the Business Logic Layer, which performs certain transformations on the object, and then interacts with the DAL to save it.

Yes, it's a little tiring , but we were wondering if this is better?

Yes . I know someone posted an EF Poco Adapter, but it's all in C #, and we would prefer a VB.NET solution.

Yes . Switching to NHibernate is the last option, as we are already deeply entering our development cycle.

+5
source share
2 answers

- POCOs. ORM , . - - - "" "". DAL , POCO - , EF.

, /NHibernate , .

+2

EF? IPOCO.

.

+1

More articles:


All Articles