Simple N-Tier design
Design and Architecture
1
Posts
1
Posters
0
Views
1
Watching
-
Hi, I'm looking for a classic and simple N-Tier design using earlier .NET architecture rather than MVC. I haven't done this for years. I was thinking of having a class with my table structure in terms of the properties/fields. Then maybe having a separate DAL class for the methods such as Read, Save, Update and Delete. In terms of the class design, if I have several tables using the same methods, is there a particular design I should follow. I realise there are many ways of achieving this but I'm looking for something simple that junior developers can follow easily. Can somebody please recommend or maybe offer a link to a good article for this? Thanks