OK, I'm well aware the most likely solution is based on master pages and themes/styles... but bear with me here.
We have an application at present to do with vehicle tracking. It's currently written in classic vanilla vbscript on good ol' asp. We have several companies that do installations for us that want to be able to offer their "own" tracking site based on ours, but with their company logo and colour scheme.
I am currently in the process of redeveloping our existing site into asp.net anyway, so it seems to make sense to build in this sort of "white labelling" exercise whilst I'm doing that.
We will, therefore, have a setup whereby our own existing site needs to sit alongside resellers of our product, utilising the same code, webserver and database server. These resellers of our product will want to use their own domain names rather than subdomaining off our domain, but they will not be able to host our code on their server, it is essential that there is only one set of code files to maintain, I do not want a situation whereby there are multiple copies of identical asp.net pages spread around that need updating every time I change one word on the page!
Utilising host-headering, I can point any relevant reseller domain to share the same starting directory on the webserver. However, if I do this then the incoming customer will start off with the same page. This won't do... Each reseller will have a starting "log in" page (hopefully all sharing the same file) but the page needs to be already skinned when that resellers customer arrives at the page. It's no good having a page with a default theme which the reseller's customer logs in on, then gets the appropriate reseller theme from that point onwards, it has to be the correct theme from the first page served up... default.aspx.
My brains a bit fudged up at present, I can't conceive of a way to use the host-headering to pre-apply the relevant theme (which is what needs to happen) by the incoming customer gets to the log-in page.
For example, customer A is a customer of "acme tracking" so he goes to "www.acme-tracking.com
" and expects to see Acme's logo up there, with their colour scheme of orange and green. However, customer B is a customer of "Tracking UK" so he goes to "ww.tracking-uk.com" and expect's to see tracking uk's logo and their colour scheme of pink and blue...
Both customers will type in their relevant URL and both will hit my server. The host header is set so that those url's are associated with my "vehicletrackingApp" sub-directory in wwwroot and they both hit "default.aspx" in that sub-directory. How can I make each one see the correct appearance for their version of the home login page?
Can I do this or do I need to have a separate subdirectory for each franchise with a separate log-in page in each one, which then redirects the customer somehow to a common "vehicletrackingcommon" subdirectory that holds the REAL files for the application?
I'm sure I'm missing an obvious solution here, but I just can't see the wood for the trees!