"First-code dry" publishes the re-grooming of. NET Web Apps in Windows Server 2016 using Web Deploy mode.

In the process of learning and work, found many colleagues, friends, when doing. NET Web application Publishing, still in the build-copy to the server way, a little more advanced, is to publish to the local, and then upload to the server

This is not only inefficient, it is not easy to version control, the program is slightly more complex, coupled with teamwork, the release will be a variety of unpredictable version issues.

Just for two days playing Azure and Windows Server 2016, see "First Dry" "Azure series" 1, feel azure again, experience Windows Server 2016 and deploy BlogEngine.NET, while I'm in the process of actually using it, Also encountered a lot of web deploy pit, so here, the full configuration of WebDeploy and use of the method to re-comb again

Of particular note is that although the Windows Server 2016 as a demonstration, but and in Windows Server R2 inside the steps are exactly the same!

Here's the complete step

1. Click inside IIS to get the new Web platform components

2. Download the Web platform components and install

3. Search for Web Deploy, find version 3.5, and install

4. Continue searching for Web Deploy version 3.6 and install

Once installed, re-enter IIS and discover some new features

5, into the Computer Management, modify the password properties of two users (Wdeployadmin and Wdeployconfigwriter), including setting never expires and set a fixed password

6. Back in IIS, reconfigure the users of some of the providers in the Management Service delegation for Web deploy (using the password you just set)

Here is only a backupsettings configuration, the other 3 people according to gourd painting scoop can be

7. Add an IIS Admin user

7. Configure the Firewall

As we can see, the default service port for the WebDeploy service is 8172

Therefore, to add a 8172 port inbound rule to the Ingress rule

The default WebDeploy program adds firewall exception handling, but if it doesn't, you'll need to add it manually.

Well, so far, the Web deploy configuration, it's done, Be sure to restart the server

The following tests are also required (see, do not go, there is one step in the test is very important to configure the permissions)

1. Create a new IIS site

It is particularly noteworthy that this IIS site is located in the directory of the folder, must have local service permissions! Otherwise, if you publish, you will be prompted for incorrect permissions!

2. In the IIS Manager permissions of the site, add the IIS Admin user just added

There's a point here. Note that IIS supports detailed permission configuration for child sites, such as having sub-applications that can be configured similarly

3. Create a new ASP. NET Web Applicaiton empty project in Visual Studio 2015 to test

Create a new Web page

4. Test release

The site name here is the site name of IIS, if it is a subweb, fill in

WebDeploy Test/Sub-site

Before you publish, it's a good idea to preview, it's a great release habit!

The last point is published and a record appears

Okay, look at the effect http://webdeploytest.printhelloworld.com/.

maidservant, posted in Blog Park and maidservant Blog

Reprint please indicate the source, welcome mail exchange:[email protected], or add QQ Group: 11444444

"First-code dry" publishes the re-grooming of. NET Web Apps in Windows Server 2016 using Web Deploy mode.