Domain Objects with Interfaces
I’m in a situation where part of my system has a dependency on another module in the same system, but the modules themselves need to remain independently deployable, where the parts they depend on would be filled in with another implementation.
How should UI layer pass user input to BL layer?
I’m building an n-tier application, I have UI, BL, DAL & Entities (built from POCO) projects. (All projects have a reference to the Entities).
Dependency injection with n-tier Entity Framework solution
I am currently designing an n-tier solution which is using Entity Framework 5 (.net 4) as its data access strategy, but am concerned about how to incorporate dependency injection to make it testable / flexible.
Service Layer – how broad should it be, and should it also be used from the local application?
The background:
Motivation for a service layer (instead of just copying dlls)?
I’m creating an application which has 2 different UIs so I’m making it with a service layer which I understood is appropriate for such scenario.
Triggering Data Changes in N-Tier
I’ve been studying n-tier architectures as of late, particularly in VB.NET with Entity Framework and/or LINQ to SQL. I understand the basic concepts, but have been wondering about best practices in regard to triggering CRUD-type operations from user input/action. So, the arcitecture looks something like the following:
Triggering Data Changes in N-Tier
I’ve been studying n-tier architectures as of late, particularly in VB.NET with Entity Framework and/or LINQ to SQL. I understand the basic concepts, but have been wondering about best practices in regard to triggering CRUD-type operations from user input/action. So, the arcitecture looks something like the following:
Good technologies for developing a modular server component in .net?
I am using WPF, Prism and Unity to develop the user interface for a .net application. The UI will run from a PC, but I also need to develop a separate complex server component that will provide services to the PC component via WCF.
Do stored procedures violate three-tier separation?
Some colleagues of mine have told me that having business logic in stored procedures in the database violates the three-tier separation architecture, since the database belongs to the data layer whereas stored procedures are business logic.
Project/DLL separation of concerns in ASP.NET MVC
I’m coming from a web forms n-tier background into ASP.NET MVC projects, and I’m wondering what the best practices are for separation of the components of MVC into different libraries (or not to) in the way one might with an n-tier model. Most of the sample apps I have seen only had one project file and objects were separated only by folder.