I have a class that inherits from DataAccessAdapter and have placed this class in the DatabaseSpecific namespace/folder. Now when I regenerate the project my data access class is set as not included in the project. So I then have to go and include the file back into the project before I can compile again. Does anyone know how to stop this from happening or is there is different place I should place my class?

tprohas wrote:

I have a class that inherits from DataAccessAdapter and have placed this class in the DatabaseSpecific namespace/folder. Now when I regenerate the project my data access class is set as not included in the project. So I then have to go and include the file back into the project before I can compile again. Does anyone know how to stop this from happening or is there is different place I should place my class?

The best place to place your extended adapter calss is your BL project. Remeber that your BL is the layer that sets between your DAL and your UI. Your UI (winforms, webforms, webservices, mobile...) references your BL and your generic DAL dlls.

omar wrote:

tprohas wrote:

I have a class that inherits from DataAccessAdapter and have placed this class in the DatabaseSpecific namespace/folder. Now when I regenerate the project my data access class is set as not included in the project. So I then have to go and include the file back into the project before I can compile again. Does anyone know how to stop this from happening or is there is different place I should place my class?

The best place to place your extended adapter calss is your BL project. Remeber that your BL is the layer that sets between your DAL and your UI. Your UI (winforms, webforms, webservices, mobile...) references your BL and your generic DAL dlls.

Thanks Omar, I'll give it a try.