Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I got a Data Access Layer that’s being formed by one DBML in which i just include all object I need. Is it necessary to write more functionality in this dbml or can I just use the dbml as my DAL? I ask this because I am currently writing functionality to, for example, get all Articles from a Table in the Business Logic Layer. So I’m kind of lost now. What kind of examples can be given so that it’s clear to me what to put in the Business Layer.
The Business Logic Layer is where you basically put your business rules and business entities. It is where you want to do things such as validity checks on making sure a user can add an Article, Edit an Article, Delete an Article, etc. The purpose is to centralize all your business rules and entities so that the Presentation Layer does not need to know about the underlining DB structure and that the DB structure is not defining the interface.
As far as if you need one you’ll need to decide that for yourself.