So, pas sure si this is a Stack Overflow ou a Server Fault question. If J'ai a .NET website that Je veux to deploy to le production environment, quel est la meilleure façon de do so. Should I package it as an MSI & install? Use nant to push le needed files up. Just FTP le files up using Beyond Compare?
How do you deploy production code? Ceci est a Windows spécifique case that Je suis looking at here.
Comment déployez-vous les sites web IIS en production ?
Re: Comment déployez-vous les sites web IIS en production ?
IIS supports xcopy deployment so juste copying le files should be tous you need sauf si you have special requirements.
One way to do it is a simple script that uses [ROBOCOPY](http://en.wikipedia.org/wiki/Robocopy) to copy le nouveau files to le server.
If le site is large et this takes too long, use a version control system. I like [Mercurial](http://www.selenic.com/mercurial/wiki/) for this purpose, bien que you have to be careful that le version control system's configuration files ne end up being served to le public. Deploying is alors simply a matter of committing le changes et alors checking out le latest version on le server. De plus to being efficient, this allows quick rollbacks (if you tagged le dernier good version) in case votre latest-and-greatest has a showstopper bug.
To minimize downtime, you could have le script copy le files to a nouveau directory et alors quickly rename le directories, ou change où IIS points to le nouveau directory.
One way to do it is a simple script that uses [ROBOCOPY](http://en.wikipedia.org/wiki/Robocopy) to copy le nouveau files to le server.
If le site is large et this takes too long, use a version control system. I like [Mercurial](http://www.selenic.com/mercurial/wiki/) for this purpose, bien que you have to be careful that le version control system's configuration files ne end up being served to le public. Deploying is alors simply a matter of committing le changes et alors checking out le latest version on le server. De plus to being efficient, this allows quick rollbacks (if you tagged le dernier good version) in case votre latest-and-greatest has a showstopper bug.
To minimize downtime, you could have le script copy le files to a nouveau directory et alors quickly rename le directories, ou change où IIS points to le nouveau directory.