Re: Deployment Best Practices

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: John Saunders (johnwsaundersiii)
Date: 11/02/04


Date: Tue, 2 Nov 2004 13:49:58 -0500


"sstevens" <sstevens@discussions.microsoft.com> wrote in message
news:EE5B641B-A7AD-4E2B-9E05-4A99887FC878@microsoft.com...
> Does anyone have suggesstions for ASP.NET deployment best practices. This
> is
> in the context of a large organization where developers do not have admin
> access to web servers. The idea of buliding msi packages for each deploy
> seems difficult to implement because the server admins do not have the
> time
> to constantly be running msi's and moving applications between
> environments.
> Are there any proven products that can automate this process for .net
> applications?

I know this response is late, but I was intrigued by your question.

You said that the system admins don't have time to be running msi's. Don't
they do installs all the time? Also, if you have an msi, can't it be run
unattended?

Of course, a better issue is that web setup projects can only install to the
default web site on a machine...

What I have done in a lower-volume production environment is:

0) Create a virtual directory on a web server accessible from the build
machine
1) Empty the VD
2) the Copy Project feature of VS.NET to copy only the "files necessary for
this project" to the VD
2a) If the VD is on a staging server, test here
3) On acceptance, have the VD copied up to a new directory in production. If
you use versioning, name the new directory to include the version,
otherwise, to include a timestamp.
0a) Production has two versions for each web application. The real one, and
the "next" one.
4) Configure IIS to point the "next" application to the newly-copied
directory.
5) Do final sanity checking
6) Configure IIS to point the "real" application to the newly-copied
directory

This worked well for a moderate volume of deployments.

John Saunders
johnwsaundersiii@hotmail.com



Relevant Pages

  • Re: Agile Methodology
    ... >>> automated testing? ... Agile teams practice "Daily Deployment", ... achieved a major milestone - production launch. ... a system going live on budget, time and within scope as a success story. ...
    (comp.software.testing)
  • Re: Temporarily Make Web Site Completely Inaccessible
    ... Make a copy of production for historical purposes; ... Overlay PROD-specific files, such as a Web.config that has PROD database ... assembly version during deployment and make that its directory name. ... and PRODwon't work until you make the schema change. ...
    (microsoft.public.dotnet.framework.aspnet)
  • managing web.config in different environments...
    ... We have 3 different environments: dev, qa, and production. ... we use qa.web.config with its respective settings. ... Now netops team that does the production deployment are recommending another ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Dotnet development
    ... VB6 application to C# (6 dll's, 1 exe). ... production for about a month and haven't had any significant issues only ... We have not had any issues with the Framework libraries ... deployment to end users. ...
    (microsoft.public.dotnet.faqs)
  • Re: error 12560 causing webservices slowdown
    ... TNS for 32-bit Windows: Version 8.1.7.0.0 - Production ... Oracle Bequeath NT Protocol Adapter for 32-bit Windows: ... if I understand correctly BEQ is meant to use locally, ... why does it happen to most web servers ...
    (comp.databases.oracle.server)