With S#arp Architecture, my understanding is that domain logic (aka business logic) that operates on more than one type of entity is best handled by the Application Services layer.
I am developing an application in WPF using the MVVM pattern. If I have Student as a data model, for example, where could I add the business logic like adding new Students, deleting Students and updat
For instance, if I want to check is the input has only alphanumeric characters and is more than 10 characters long. Should I just check it server-side? Or server-side and in the database (query) itsel
I need to write a static method which is performing some kind of parsing on a string with signature like:
I\'ve inherited an asp.net web solution, which has business logic and data calls as seperate assemblies. In the busine开发者_StackOverflowss layer there are a small number of calls to get/set HttpCont
We have been looking a several case studies that claimvast improvements if you implement your Line-Of-Business applications in xRM开发者_Go百科.
In trying to understand Domain Driven Design I keep returning to a question that I can\'t seem to definitively answer.
In Entity Framework, is it possible to make the framework inject the DbContext into each object (entity) that is attached to or retrieved from the Context?
Hello I am a newbie to n-tier architecture and was trying to find out the difference between what an application server hosting application layer of code does, and what a web service does?
So I have this general question of where should I have certain logic for example - var data=GetItems();
加载中,请稍侯......