.net - Where should the DAOs go in a project structure? -


I am working on a project in VBnet and need to implement DAL. I am not sure where my project is the best place to stick to the DAO. Should I touch the DAO in the same namespace as is the use of business items that are going to use them. Or should I add all the DAOs together.

I have a Java background that can stain your own understanding. :)

I always try to keep things clean and good, you have some type of modular design Should try, even if it is a small project. I have lit my fingers many times.

Example: PG. Customer CareE.DAL & lt; - Data access layer

PG.CustomerCare.BO & lt; - Business Objects & lt; - It can take the place of services.

PG. customer service. Services - Services for business logic, this will be a reference for the table

PG.CustomerCare .client.Web

PG.CustomerCare.Client.Winforms & lt; - Here, only contact the service level.


Comments

Popular posts from this blog

sql - dynamically varied number of conditions in the 'where' statement using LINQ -

asp.net mvc - Dynamically Generated Ajax.BeginForm -

Debug on symbian -