Click here to Skip to main content
15,867,453 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
Hi,

I have a scenario which I am sure is fairly common but I am struggling to find good information on it.

I have a website which is by necessity composed of several separate websites when deployed on my production server (i.e. parts of the website are accessible directly via their own conventional domain, e.g. www.adomain.com, www.anotherdomain.com).

On my development machine (Windows 7 Ultimate with, I think IIS 6, though I'm not sure how to check this), the website is organised as separate projects within a single solution. If I deploy this to my localhost IIS, all of the URLs that go between projects have the form localhost/something. Clearly these need mapping to the correct domains when I deploy. Is there a recognised way of handling this kind of thing? It must be extremely common and yet I don't seem to be able to find any good articles on how to handle this.

I have ideas how to bake my own solution but I don't want to reinvent the wheel if I can avoid it.

I would be extremely grateful for any advice or pointers to useful information.

Kind wishes, Patrick
Posted

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900