D
David
I will be creating/maintaining web sites for clients who are in the same
industry. So although they are separate business entities, their business
models are very similar.
So I would have different database backends, obviously. But I would like to
somehow come up with a good way to create web applications with a high
degree of maintenanbility. So hopefully not a lot of copying and pasting.
Does it make sense?
As a starter
- One namespace for the business tier class library. This will store all
business rules that are common to my clients
- A separate business tier library for each client with client specific
variations. Class inheritance will be used for this purpose.
Well, the business tier is the easier part because of class inheritance, but
the presentation layer with ASP.NET presents a huge dillema since ASP.NET
does not support visual inheritance.
I am open to hearing about a creative approach to solve this. Thanks.
industry. So although they are separate business entities, their business
models are very similar.
So I would have different database backends, obviously. But I would like to
somehow come up with a good way to create web applications with a high
degree of maintenanbility. So hopefully not a lot of copying and pasting.
Does it make sense?
As a starter
- One namespace for the business tier class library. This will store all
business rules that are common to my clients
- A separate business tier library for each client with client specific
variations. Class inheritance will be used for this purpose.
Well, the business tier is the easier part because of class inheritance, but
the presentation layer with ASP.NET presents a huge dillema since ASP.NET
does not support visual inheritance.
I am open to hearing about a creative approach to solve this. Thanks.