Shulou(Shulou.com)06/01 Report--

This article mainly explains "how to deploy ASP.NET Core program to Windows system". The content of the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "how to deploy ASP.NET Core program to Windows system".

First, create a project

Choose the ASP.NET Core Web application when creating a new project, as shown in the following figure:

Configure the new project interface to set the project name and location, as shown in the following figure:

Select ASP.NET Core 3.1 under the .net Core framework to create an API project, and uncheck "configure for HTTPS", as shown in the following figure:

This creates a Web Api project, and we visit the project:

The browser can be accessed normally, indicating that there is no problem with the project we created, and then we deploy the project to the windows system.

Release the project

We created a Web Api project above, and let's release the project first. There are two release and deployment modes for ASP.NET Core projects, which will be explained in the following sections.

1. Framework dependence

Framework dependency (FDD): short for Framework-dependent deployments. This publishing method relies on the Framework framework, which means that the server to be deployed must follow the ASP.NET Core runtime environment (ASP.NET Core Runtime). This deployment is recommended by Microsoft by default. Let's take a look at how to deploy using framework dependencies.

We right-click on the project and select "publish":

The publish target selects publish to folder, publish the file to FDD folder, and then click Advanced:

In the release interface, the deployment mode selection framework depends on, and the target runtime selects the default portability:

We see that there are many options below the target runtime, and select "Portable" here, which means that the compiled files can be deployed to the windows platform, Max platform, and Linux platform. If you only want to deploy to one platform, you can choose a specific platform. For example, if you only want to deploy to the x64 architecture of the Linux system, select "linux-x64".

Finally, click the "Save" button, and then publish:

In this way, the release is successful in the FDD way. Let's take a look at the released file:

As you can see, there are very few files after the framework is released in a dependent manner.

2. Independent deployment

SCD: an abbreviation for Self-contained deployments. This approach means that the runtime environment is provided independently, that is, the server to be deployed can be deployed without having to install the ASP.NET Core runtime environment. Since there is no need to pre-install the runtime environment, the file size compiled by this release will be larger than that compiled by the framework-dependent method. At the time of release, the deployment mode can be independent:

At this point, there is no portable option for the target runtime, and since we are deploying on top of the windows system, we choose win-x64 here. Finally, save the release. After the release is complete, let's take a look at the released file:

As you can see, there are a lot of files after release, because some dll folders that programs need to run will be packaged at the time of release.

3. Deployment 1. Configure the deployment environment

In the above steps, we have released the program to a folder and deploy it below. Let's first demonstrate how to deploy using the FCD pattern. The FCD pattern needs to rely on the Framework framework, and since we are just deploying, we only need to install ASP.NET Core Runtime, not SDK. First of all, we need to install ASP.NET Core runtime on the server and download the corresponding version from Microsoft's official website to install it. Select ASP.NET Core Runtime 3.1 here:

Choose to download Hosting Bundle here. Because Hosting Bundle includes. Net Core runtime and IIS support.

After the download is complete, double-click the exe file to install:

After the installation is complete, we enter the following command on the command line to check whether the installation is successful:

Dotnet-info

As shown in the following figure:

You can see the prompt that we have installed the. NET Core runtimes environment, not SDK.

Since we need to deploy to IIS, restart the computer after installation, or restart the IIS service using the following command line:

Net stop was / ynet start w3svc

As shown in the following figure:

Note: run the command line as an administrator, otherwise an error denying access will be reported

You can also manage the restart and start IIS in the server, as shown below:

2. Console deployment

Let's deploy using the console first. Enter the post-release path and execute the following command to start it on the command line:

Dotnet dll file name

As shown in the following figure:

You can see that the project has been started and is listening to port 5000. We access the following url address in the browser: http://localhost:5000/weatherforecast

You can see that the information can be returned normally.

When testing here, it is deployed on the Windows server. If it is deployed on a personal computer, it will be displayed directly in the web page when browsing in the browser.

We deploy the program to the server, which can be browsed on the server, so can we browse it on the remote computer? We browse on the remote computer:

It can be seen that our visit is denied. Why? Because the listening IP address is localhost, if you want the remote computer to be accessible, you also need to use the urls parameter to set it:

The * sign is used here, which means that any URL can be accessed. Let's visit it again:

This time we can visit. You can also specify the port number to access using the urls parameter. For example, if you want to listen on port 8090, you can use the following command:

Dotnet AspNetCoreDeployDemo.dll-- urls http://*:8090

Deploying programs directly to the console is generally suitable for our own development and debugging programs, which is not recommended in a real production environment. In this way, the Kestrel server handles the HTTP request directly. In the windows system, we usually deploy the ASP.NET Core program on IIS, and IIS is used as a reverse proxy server. Let's take a look at how to deploy to IIS.

3. Deploy to IIS

In traditional .NET Framework, ASP.NET programs are published on IIS and are hosted by IIS's worker process (w3wp.exe), which can be found in the task manager. In the ASP.NET Core program, it is no longer hosted by the IIS worker process, but runs using the self-hosted Web server (Kestrel). IIS is used as a reverse agent to forward requests to ASP.NET Core programs in different ports of Kestrel, and then push the received requests to the middleware pipeline. After processing the request, the HTTP response data is written back to IIS, and finally transferred to different clients through IIS. In this process, the most important role is AspNetCoreModuleV2 (before asp.net core 2.0, AspNetCoreModuleV2,asp.net core 2.x is AspNetCoreModule, and it has been changed back to AspNetCoreModuleV2 since 3.0. it is a module in IIS that forwards HTTP requests as soon as they enter IIS and is quickly redirected to the ASP.NET Core project. Because IIS is only responsible for forwarding requests as a reverse proxy, not listening to HTTP request ports, there is no need to use application pools to host our code.

After the asp.net core runtime is installed on the computer, there will be AspNetCoreModule in the module of IIS:

Double-click "Module" to see if there is an AspNetCoreModule module in it:

Next, add a website to IIS, as shown in the following figure:

Finally, click the "OK" button to complete the website and deployment. We browse in the browser:

So you can access it.

In previous versions of ASP.NET Core 3.x, after deploying the website, we also needed to set up the application pool and set the .NET CLR version to "unmanaged code". In the version starting with ASP.NET Core 3.x, there was no need to set up the application pool and the website could be accessed directly after deployment. We can also set the application pool to "unmanaged code", as shown in the following figure:

4. Independent deployment

The above two deployment methods are based on the framework relying on the released files. We are looking at how to deploy using the released files of independent deployment. We see that there is an exe file after release:

When we double-click the exe file, we will see that it starts directly in the console:

At this point, you can access it in the browser. This makes it possible to deploy, and this approach is not recommended in real production.

Thank you for your reading, the above is the content of "how to deploy ASP.NET Core programs to Windows systems". After the study of this article, I believe you have a deeper understanding of how to deploy ASP.NET Core programs to Windows systems, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.