Article Discussion: Creating Test and Production Sites with Only One IIS Server

The need to separate live code from development code cannot be stresses enough. However, depending on the project, the size of the company, or just plain old budgetary constraints, it may be fairly infeasible to have an entire server dedicated solely to developing and enhancing code. This article will show you how you can obtain the necessary 'buffer zone' in your application, with only one server. This includes both the code, and the database!


Read the full article here: Creating Test and Production Sites with Only One IIS Server

Hi

How about using a subdomain for your test site like www.company.com and test.company.com.

I realise that this would add the extra step of making changes to your DNS but it would be easier to address from the browser and about the same level of security separation ( i.e. copying web.config between sites could make for a real disaster). Are there any pros/cons that I have missed? Yes I was thinking of using a subdomain and now I am in two minds, and they say two heads are better than one !!

Regards