Shulou(Shulou.com)05/31 Report--

This article mainly explains how to upgrade the .NET Core 2.0 project to. NET Core 2.1. the content in 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 upgrade the .NET Core 2.0 project to. NET Core 2.1"!

Step by Step

1. Modify our project goal framework

During the process of updating VS 2017, our .NET Core version will also be updated. Of course, if you do not have the .NET Core 2.1SDK installed on your computer, you will need to download the latest version of SDK from the official website to install it.

Once we have installed our .NET Core 2.1 SDK, we can change the target framework of our original program to .NET Core 2.1.

By right-clicking on our project, we can edit the csproj file directly or make visual changes by opening the properties option. In fact, here we edit through the properties page is essentially editing our csproj file.

At the same time, in order to maintain the consistency of our project framework, we need to modify the target framework of the class library we reference to .NET Core 2.1 as well.

Replace the Nuget package reference

In version 2.1 of the .NET Core, Microsoft replaced Microsoft.AspNetCore.All, the basic DLL of the .NET Core, with Microsoft.AspNetCore.App, so after updating the program's target framework, we also need to remove the reference to Microsoft.AspNetCore.All and add a reference to Microsoft.AspNetCore.App.

The following Nuget package is not included in the Microsoft.AspNetCore.App. If you need these package, you can refer to these package in the project.

one

two

three

four

five

six

seven

eight

nine

ten

eleven

twelve

thirteen

fourteen

fifteen

Microsoft.AspNetCore.ApplicationInsights.HostingStartup

Microsoft.AspNetCore.AzureAppServices.HostingStartup

Microsoft.AspNetCore.AzureAppServicesIntegration

Microsoft.AspNetCore.DataProtection.AzureKeyVault

Microsoft.AspNetCore.DataProtection.AzureStorage

Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv

Microsoft.AspNetCore.SignalR.Redis

Microsoft.Data.Sqlite

Microsoft.Data.Sqlite.Core

Microsoft.EntityFrameworkCore.Sqlite

Microsoft.EntityFrameworkCore.Sqlite.Core

Microsoft.Extensions.Caching.Redis

Microsoft.Extensions.Configuration.AzureKeyVault

Microsoft.Extensions.Logging.AzureAppServices

Microsoft.VisualStudio.Web.BrowserLink

When referencing Microsoft.AspNetCore.App, we may prompt that some dependencies are missing or that the original referenced version of the Nuget package does not meet Microsoft.AspNetCore.App. We just need to add our missing dependencies or upgrade versions that do not meet the requirements according to the error message prompted.

For example, when I upgraded the PSU.EFCore class library, I found that the version of the referenced assembly did not satisfy our use of the 2.1.6 version of Microsoft.AspNetCore.App. We just needed to upgrade these referenced DLL and install our latest version of Microsoft.AspNetCore.App.

After installing the .NET Core 2.1 SDK, the following tools has been included in the latest version of the .NET Core CLI, so we can delete these referenced Nuget packages under the DotNetCliToolReference node in the csproj file.

one

two

three

four

Microsoft.DotNet.Watcher.Tools (dotnet watch)

Microsoft.EntityFrameworkCore.Tools.DotNet (dotnet ef)

Microsoft.Extensions.Caching.SqlConfig.Tools (dotnet sql-cache)

Microsoft.Extensions.SecretManager.Tools (dotnet user-secrets)

For the dotnet-aspnet-codegenerator (used to generate controllers and views templates in MVC) Nuget package under the DotNetCliToolReference node, you can also choose to delete this reference and use the global installation tool instead.

one

Dotnet tool install-g dotnet-aspnet-codegenerator

III. Changes based on ASP.NET Core 2.1Code conventions

After the .NET Core was upgraded to version 2.1, ASP.NET Core was updated accordingly, and some of the underlying code in the template we created was modified. For example, in the following example, the Program.cs code structure in the MVC project we created using the .NET Core version 2.0 is somewhat different from the template code generated using the .NET Core 2.1.

one

two

three

four

five

six

seven

eight

nine

ten

eleven

twelve

thirteen

fourteen

fifteen

sixteen

/ / ASP.NET Core 2.0

Namespace WebApp1

{

Public class Program

{

Public static void Main (string [] args)

{

BuildWebHost (args) .Run ()

}

Public static IWebHost BuildWebHost (string [] args) = >

WebHost.CreateDefaultBuilder (args)

.UseStartup ()

.build ()

}

}

one

two

three

four

five

six

seven

eight

nine

ten

eleven

twelve

thirteen

fourteen

fifteen

/ / ASP.NET Core 2.1

Namespace WebApp1

{

Public class Program

{

Public static void Main (string [] args)

{

CreateWebHostBuilder (args). Build (). Run ()

}

Public static IWebHostBuilder CreateWebHostBuilder (string [] args) = >

WebHost.CreateDefaultBuilder (args)

.UseStartup ()

}

}

Here we modify our Program.cs code structure according to the latest version of the template code.

Similarly, ASP.NET Core 2.1 adds support for GDPR in Startup.cs files (an EU policy that when we need to collect user data, we must explain to users in "concise, transparent and easy-to-understand form, clear and plain language", for example, here we use cookie and session to store user data, we need to inform users in advance) Redirect support for HTTPS and the addition of the SetCompatibilityVersion method allows applications to choose to join or exit the potentially disruptive behavior changes introduced in ASP.NET MVC Core 2.1 + (well, I still don't know what it is after looking around).

IV. Other changes

In the update of the version of the ASP.NET Core MVC framework, some of the referenced JS libraries have also been upgraded, so I will not upgrade here, mainly to add hints on GDPR policies for our program. And require our program to be accessed in the form of HTTPS.

First, we create a distribution view _ CookieConsentPartial to prompt us that we need to collect user information, add an Action in the SecretController controller to display our privacy policy, and reference the created distribution view in our template page. The style here does not make any adjustments, just as an example.

one

two

three

four

five

six

seven

eight

nine

ten

eleven

twelve

thirteen

fourteen

fifteen

sixteen

seventeen

eighteen

nineteen

twenty

twenty-one

twenty-two

twenty-three

twenty-four

twenty-five

twenty-six

twenty-seven

twenty-eight

twenty-nine

thirty

thirty-one

thirty-two

thirty-three

thirty-four

thirty-five

thirty-six

thirty-seven

thirty-eight

thirty-nine

forty

forty-one

@ using Microsoft.AspNetCore.Http.Features

@ {

Var consentFeature = Context.Features.Get ()

Var showBanner =! consentFeature?.CanTrack? False

Var cookieString = consentFeature?.CreateConsentCookie ()

}

@ if (showBanner)

{

Toggle cookie consent banner

Use this space to summarize your privacy and cookie use policy.

Learn More

Accept

(function () {

Document.querySelector ("# cookieConsent button [data-cookie-string]") .addEventListener ("click", function (el) {

[xss_clean] = el.target.dataset.cookieString

Document.querySelector ("# cookieConsent") .classList.add ("hidden")

}, false)

) ()

}

one

two

/ / reference the distributed view in the home page (login page) of the website

one

two

three

four

five

six

seven

eight

nine

/ / /

/ / Privacy Policy

/ / /

/ / /

[AllowAnonymous]

Public IActionResult Privacy ()

{

Return View ()

}

In the previous steps, we supported the use of HTTPS requests for access in our code, and now we can enable SSL to enable us to access our project through HTTPS requests.

Thank you for your reading. the above is the content of "how to upgrade a .NET Core 2.0project to .NET Core 2.1". After the study of this article, I believe you have a deeper understanding of how to upgrade a .NET Core 2.0project to .NET Core 2.1.The specific usage still 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.