What are the advantages of strictly maintaining separate data | algorithm | interface layers?
I always separate the user interface from other functionality in my programs – its the way I have been taught, and it has obvious advantages since you can change the interface but keep the same functionality.
How to handle errors best addressed in a higher abstraction layer and dependent on state inferred in current layer?
I have a use-case that can be repaired, but the logic for repairing it is best done in a higher level of abstraction. Just throwing exception/failure is ugly because it’s hard to pass back up through the stack the information needed for the parent-layer to know how to fix it.
How to handle errors best addressed in a higher abstraction layer and dependent on state inferred in current layer?
I have a use-case that can be repaired, but the logic for repairing it is best done in a higher level of abstraction. Just throwing exception/failure is ugly because it’s hard to pass back up through the stack the information needed for the parent-layer to know how to fix it.
Can a layer consist of multiple projects / dlls?
I am working on the architecture for a new web application and I am pretty much a complete newbie when it comes to architecture. Working my way through .NET Application Architecture Guide, 2nd Edition and learning a lot. I have decided to go for the “standard” 3-layer architecture: Presentation layer, Business layer, Data layer. Will be using ASP.NET MVC and Entity Framework.
Can a layer consist of multiple projects / dlls?
I am working on the architecture for a new web application and I am pretty much a complete newbie when it comes to architecture. Working my way through .NET Application Architecture Guide, 2nd Edition and learning a lot. I have decided to go for the “standard” 3-layer architecture: Presentation layer, Business layer, Data layer. Will be using ASP.NET MVC and Entity Framework.
Can a layer consist of multiple projects / dlls?
I am working on the architecture for a new web application and I am pretty much a complete newbie when it comes to architecture. Working my way through .NET Application Architecture Guide, 2nd Edition and learning a lot. I have decided to go for the “standard” 3-layer architecture: Presentation layer, Business layer, Data layer. Will be using ASP.NET MVC and Entity Framework.
Confused about layered application development
So, for the first big project that I’m getting paid for, I decided I’d do things right.
Confused about layered application development
So, for the first big project that I’m getting paid for, I decided I’d do things right.
Confused about layered application development
So, for the first big project that I’m getting paid for, I decided I’d do things right.
Confused about layered application development
So, for the first big project that I’m getting paid for, I decided I’d do things right.