Is the tier design approach good for a windows app? [modified]
-
We are converting our system over to C# and I am wondering if the the tier design is worth the extra trouble. And it seems most of the applications I see designed this way are mainly web apps. -- modified at 9:09 Tuesday 13th June, 2006
It is still good to practice it. For instance a method of saving plus data validation/calculation/error handling of a transaction can be used in 1) Importing from external file 2) transaction entry screen 3) outside of the transaction entry screen where you want to batch saving transactions 4) using the method in a windows service to process transactions in background. At least if you need to change something, you don't have to go through all 4 area.
-
We are converting our system over to C# and I am wondering if the the tier design is worth the extra trouble. And it seems most of the applications I see designed this way are mainly web apps. -- modified at 9:09 Tuesday 13th June, 2006
Model View Controller... It may not seem necessary now, but as that project grows, it will become increasingly evident just how helpfull it can be for maintenance if nothing else. Believe me, it's worth the extra trouble, it will be more trouble in the long run without it. Visit BoneSoft.com