bll | 易学教程

Do you allow the Web Tier to access the DAL directly?

阅读更多关于 Do you allow the Web Tier to access the DAL directly?

I'm interested in perceived "best practice", tempered with a little dose of reality here. In a web application, do you allow your web tier to directly access the DAL, or should it go through a BLL first? I'm talking specifically of scenarios where there's no "business logic" really involved -- such as a simple query : "Fetch all customers with surname of 'Atwood'". Scenarios where there's any kind of logic absolutely are gonna go through the BLL, so lets call that moo . While you could encapsulate this method inside a BLL object, it seems to be somewhat pointless when often the signature will

Use BLL functions without reference the DAL in my API

阅读更多关于 Use BLL functions without reference the DAL in my API

问题 I have 3 project (C#) API, BLL and DAL. The DAL reference the DAL and the API reference the BLL. In my API I need to use all the CRUD functions but I can't use the function from my BLL because VS said that "The type "blabla" is defined in a assembly that is not referenced. You need to add the reference (DAL)" but I don't want to referenced the DAL in API project. Is there a way to do it without use my DAL project ? 回答1: In my view, what you are trying to achieve is good way to architect the

BLL, DAL, OBJ and 3 layer architecture

阅读更多关于 BLL, DAL, OBJ and 3 layer architecture

问题 My question is about 3 layer architecture. My project is briefly something like the below, however what annoyed me is after I insert a new column inside my database, I have to update those all fields except for the BLL. In the presentation layer, I created an OBJ as well as inside the DAL plus inside the DAL, there is an SQL query. I have to update all those fields manually. If I do it the 'normal' way, I put all those inside the presentation layer and update all in one place. Am I applying