从 ASP.NET Core 2.2 迁移到 3.1 [英] Migrating from ASP.NET Core 2.2 to 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.实际上微软鼓励逐个版本迁移.

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.

这篇关于从 ASP.NET Core 2.2 迁移到 3.1的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！