Three-Tier Architecture using entity framework asp.net

Example by using Three-Tier Architecture using Entity Framework.

[salmanahmed]

HI Friend, your presentation is good but lack in one understanding issue. It is that in Presentation layer why we are including the Data Access Layer. The Presentation should not know the data access layer it talk with BLL and then BLL retrieve the information from DLL. That's is what real architecture design should be.

[amiltonjbc]

I am Brazilian, Your Video Lesson is very good.
Parabens!

[MrAbugaarith]

The POCO object or even DTO object should be used to transport data between the layers, and since your POCO objects are in your DAL, you have to reference DAL everywhere...rather split it away from DAL...

[Makku]

Do you know the essential difference between N-Tier and DDD architecture?. I mean how they handle Entity Framework. One of them handle it on the BLL right?. I have a confusion about it, please.

[ayerli]

Hi Shivam,  

It's a very useful video including useful tips. However, I don't think that your sample actually demonstrate a true 3 tier separation.

Since UI is using the entity classes from DAL, it is tightly coupled to DAL. 
You could as well keep your DAL and BL in the same assembly and that would make NO difference at all.

You may want to consider moving your entities to a separate assembly POCO which is then referenced by all these 3 layers (DAL, BL, UI) and used for passing data between them.   

[shivamsrivastava]

Hello Reza yazdani 
Thanks for asking Question .

In tree Tire Architecture we can not access Data Layer Directly. We have to access Data layer through Business Layer . This will reduces coupling in our code.

Thanks

[iambackuonly]

Nice video. Liked this demo. Hope you'll use TIER instead of TIRE.. :-)

[mukeshkumarmukeshkumarjha]

this video is very useful for me.. can you plz provide a tutorial on how to insert the the values of some text fields into the database  using entity framework 3-tier architecture

[MrAbugaarith]

Not bad for a start. However you should split your entities generated by EF into its own layer, so the POCO objects will be in their own layer, this way you don't need to reference DataAccessLayer directly in UI/front end.

[Makku]

Have you heard about 4DD arquitecture?.

[Devbhagat]

3 Tier.... not TIRE. . Thanks much !
Also, Do we need to include DataLayer reference UI part.
toList method gives you all the columns, What if I want to expose only few columns of a table... How to do that?

[dmax]

Why don't we consider the Entity Data Model (EDM) as the data access layer and make the business layer access the EDM directly?

[rezayazdani]

You should not add data access layer to UI layer .It is not correct.
UI only should have a reference of Business layer.

[maazthenxt]

Its not a correct example of three layer architecture. Its violating layer architecture rules.