application-layer | 易学教程

Linq To Sql - Making a dynamic search for the Application layer without exposing DAL layer as DLL

阅读更多关于 Linq To Sql - Making a dynamic search for the Application layer without exposing DAL layer as DLL

问题 Linq to SQL, C#. I have 3 layers: DAL,BL,Application. I want to build functions of search in the BL for each table so those functions get as a parameter 'where' expresstion from the Application layer. The advantage in this approach is one function for each table so the client can search in a free and dynamic way insted of givving him 5 (for example) ways; restrict his search. For that I need to give my Application layer a DLL of my DAL layer. Doing that is not a good approach to solve the

How the Application layer will be able to dynamicly query the DB in the DAL layer?

阅读更多关于 How the Application layer will be able to dynamicly query the DB in the DAL layer?

问题 C#, LINQ to SQL Some advice me to open new topic insteed that topic becouse there is no solution for my problem. Now I will need your help to re-design my layers. Linq To Sql - Making a dynamic search for the Application layer without exposing DAL layer as DLL My project consist of 3 layers: DAL, BL, Application. The Linq2Sql is exsist in the DAL layer and he auto-generate a class to each table in the data base, and a ContextObject to manage the data base. I cant change anything in this

In which layer should Specification Pattern objects be “new'ed up”?

阅读更多关于 In which layer should Specification Pattern objects be “new'ed up”?

问题 So, I've looked at some posts about the Specification Pattern here, and haven't found an answer to this one yet. My question is, in an n-layered architecture, where exactly should me Specifications get "newed" up? I could put them in my Service Layer (aka, Application layer it's sometimes called... basically, something an .aspx code-behind would talk to), but I feel like by doing that, I'm letting business rules leak out of the Domain. If the Domain objects are accessed some other way

In which layer should Specification Pattern objects be “new'ed up”?

阅读更多关于 In which layer should Specification Pattern objects be “new'ed up”?

So, I've looked at some posts about the Specification Pattern here, and haven't found an answer to this one yet. My question is, in an n-layered architecture, where exactly should me Specifications get "newed" up? I could put them in my Service Layer (aka, Application layer it's sometimes called... basically, something an .aspx code-behind would talk to), but I feel like by doing that, I'm letting business rules leak out of the Domain. If the Domain objects are accessed some other way (besides the Service Layer), the Domain objects cannot enforce their own business rules. I could inject the