How do you Manage Production and Development Versions of Applications

[bay_dar]

We are wondering what is the best way to go about managing production
and development versions of our ASP.NET applications. We often publish
a production version of a .NET application but then we may need to make
longer term upgrades to the application that may take several weeks. Of
course in the mean time, we might have to make a quick update to the
production code, but we don't want to publish our longer term
upgrades yet.

Currently, I've been creating a copy of the files that needs the
longer upgrades and giving them temporary names such as
new_SandBox_routine. But this can get a little cumbersome as other
pages link to the original SandBox_routine file.

We have Visual Source Safe integrated into our environment so we could
use that to our advantage some how perhaps.

Of course another thing we could do is have completely different spaces
for development and production versions, but it seems to me it would be
tricky when it was time to copy the development version to the
production version - wouldn't want to miss anything.

How do you go about managing your production and development versions?

Thanks,

Bay

 

[fallenidol]

http://www.ifi.uio.no/in219/h00/verktoy/doc/html/doc/user/gs/parallel.html