vs using Web Deploy publishing

The background is this, the company has two servers, usually a spare, and another one to do the main production machine. When there are a lot of patches or things to install that need to be restarted, turn on one of them to shut down IIS directly and then reboot, and another is responsible for handling the user request.

Before a server A Web site, the release is remote up, and then copy the development machine Pubish directory files in the past. There are several drawbacks to this situation:

1. The amount of files copied in the past is huge.
2. The Web. config is difficult to control, although the connection string is controlled using release and debug, but must not be as formal as Web. config.
3. Every time you log in to a remote machine, sometimes the Clipboard cannot be shared, you need to use a drive share to copy the file, and then unzip the operation. Prone to problems.

What's changed when you publish with Web deploy:

1. Eliminates the need to remotely log on to servers, reducing the chance of errors. Multiple servers are published with high efficiency.
2. Significantly reduced file size.
3. Control vs commits an SVN version before publishing, using SVN as a backup, and the next time something goes wrong, just roll back to the previous version and then publish.
4. Multiple sites are easy to operate and do not require multiple folders to be switched back and forth.
5. I don't know if it's an illusion, I feel a lot faster to publish.

The method used

Environment needs:

1. Web Platform Installer. (Web PI, in fact, is used to install Web deploy, but I do not use, I downloaded directly on the official website)
2. Install the Management Service
3. Install Web Deploy.

Operation:

1. If you have a Web PI, use it directly to install Web deploy 3.5 before installing Web deploy 3.6. (This must be the case, otherwise there will be 404 of problems, because 3.6 of the inside there are many components provided by 3.5).
2. If you don't have a web PI, or don't want to install it, search the Microsoft website for Web DEPLOY3.5 and 3.6 and install it separately.
3. Detection system "service" in [Web Management ...] have not opened, if not open, please open.
4. In IIS, select the server node, then open "Manage service" inside the content, stop the service in the right action bar, and select the "Enable remote connection" front check box. Then select the following using Windows credentials or IIS users. Point to the right of the app, and then start the service.
5. Select the site node for the site you want to publish, open IIS Manager permissions in the content, right-click the mouse, select Allow users, and then enter the IIS user or the user for Windows. This user will be used as a credential for remote publishing in VS.
6. Open VS, right-click the project name, click Publish, enter the IP address of the server, enter the username and password, enter the site name of the site in the site name, and if it is a two-level site of the virtual directory, use/separate the name.
7. Then click "Verify Connection" in the VS release, and if successful, OK. Unsuccessful, look at the problem, Baidu is generally not the answer, at this time, Google Bar. Database connection string in the published interface remember to change AH ~~~~~

vs using Web Deploy publishing