Investigating possible architecture for an ASP.NET web solution.
I am familiar with the architecture of two multi-site systems. Neither are
by any means ideal. One is pure Classic ASP and the other is Classic ASP +
VB6 DLLs.
Pure ASP: This utilised a complete copy of the ASP code set for each
customers' site.
Mixed ASP + VB6 DLLs: This utilised a separate site for each customer's
site that contained a single ASP page. This page simply called a public
function in a common DLL which returned an HTML string. The DLL knew how to
format the page based on the referral URL containing the ASP page.
Now, what about an ASP.NET solution? I'd obviously like to centralise all
common code, and to this extent it's obvious that I'd centralise the
business and data tiers. However, I'm assuming that I'd have to put all the
ASPX pages (UI) in each dealer's site, despite the fact that many of these
will be identical. The page controller stuff (UI Process block) could
either be common or duplicated. Does anyone have any suggestions as to
which way to go?
Many thanks
Griff