从ASP.NET Core 2.2迁移到3.1

本文介绍了从ASP.NET Core 2.2迁移到3.1的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我们目前有一个 ASP.NET Core 2.2 Web应用程序，我们希望将其迁移到 3.1 (因为它较新，并且包含多个增强功能).有关于从 2.2 迁移到 3.0 的文章，但没有有关从 2.2 迁移到 3.1 的文章.

We currently have an ASP.NET Core 2.2 web app that we would like to migrate to 3.1 (as it's newer and contains several enhancements). There are articles on migrating from 2.2 to 3.0 but not 2.2 to 3.1.

首选迁移路径是先升级到 3.0 然后升级到3.1吗?在 2.2 和较新的 3.0 / 3.1 框架之间似乎存在许多不兼容性.

Is the preferred migration route to upgrade to 3.0 first then upgrade to 3.1? There seem to be a lot of incompatibilities between 2.2 and the newer 3.0 / 3.1 frameworks.

是否存在将现有 ASP.NET Core 2.2 Web应用程序升级到 3.0 / 3.1的最佳实践/一般准则?

Are there any best practices / general guidelines for upgrading an existing ASP.NET Core 2.2 web app to 3.0 / 3.1?

推荐答案

没有官方文档可以直接从2.2迁移到3.1.实际上，Microsoft鼓励逐个版本迁移.

There is no official documents to directly migrate from 2.2 to 3.1. Actually microsoft encourage migrate version by version.

大多数中断更改是在从2.2迁移到3.0 ，然后 3.0到3.1 仅具有一些配置更新(您可以很容易地看出3.0到3.1的迁移文档比2.2至3.0).通常，软件包参考更新和框架版本从3.0升级到3.1.

Most break change are made when migrate from 2.2 to 3.0, and 3.0 to 3.1 only have some config updates(you can easily tell that 3.0 to 3.1 migrate docs are much more shorter than 2.2 to 3.0). Mostly a package reference update and framework version update from 3.0 to 3.1.

简而言之，如果您是从2.2迁移到3.1.完成2.2到3.0贡献了您必须完成的工作的90％，3.0到3.1仅仅贡献了整个迁移的10％.3.0和3.1之间的主要更改是 SameSite 属性.

Briefly speaking, if you are migrating from 2.2 to 3.1. accomplish 2.2 to 3.0 contributes 90% of the work you have to do, 3.0 to 3.1 just contributes 10% of the entire migration. Major change between 3.0 and 3.1 are SameSite attribute.