The asp.net mvc project is remotely released to the windows server, asp. netmvc
Reference
- Learn about MVC here -- Summary of the most comprehensive ASP. net mvc tutorial on the whole network
- Remote Deployment of ASP. net mvc 5 Project
- Configure the Web deployment Handler
Equipment and Environment
- A desktop with windows server 2012 installed
- A desktop with win10
- Use the software on win10: visual studio2017 (2015 is also possible)
Deployment on windows server (Multi-chart warning) Step 1. Install windows server 2012 and configure the environment
1. After the installation is complete, a server dashboard will appear, and you can add roles and functions.
2. Add roles and functions
Note: you may need to restart the server before and after installation.
Step 2. Check whether the service is successfully installed
After the roles and functions are installed, there will be IIS items on the left side of the dashboard. Click the tool in the upper right corner to enter the IIS manager.
Step 3: temporarily configure windows server to enter windows 10.
1. Install visual studio2017. In this article, the free version of the 2017 Community version is installed (2015 is also similar to the configuration)
2. Create an mvc project. In the column of the article, you have provided a very good tutorial without any reference. Here, you just set up the most primitive project.
3. Start creating a project
Note: There are many ways to publish data through the file system or through Ftp. The file system is the simplest and many people are estimated to use it, as long as it is released on the local machine, you can drag it to the server, but if you have used IIS to publish it to a remote server, you will never drag the folder again.
Step 4: Go back to windows server, create a site, and install web deploy
1. Create a site
2. Configure the user (this user will be used for connection later)
3. Install web Deploy
This is the installation address http://www.iis.net/downloads/microsoft/web-deploy
Make sure to select the full version during installation. Otherwise, the connection will still fail.
4. After web Deploy is installed, check the service again. web deployment that has not appeared before will appear. Start it.
Step 5: publish in visual studio2017
Verify the connection. The connection is successful at this time.
Click Next for release speed. If you are confident that the release is successful, an unauthorized error message will appear.
It seems like this: the specified application contentpath is not used when you use the web Management Service for connection ..................
Step 6: Modify the Management delegate rules on windows server
Post after successful assignment
After adding the rule, publish it again.
Summary
We recommend that you use this method for release when the tests are frequent and the changes are frequent.