简体繁体 English

.Net 5 发布后.Net Core 3 网站会发生什么？

[英]What will happen to .Net Core 3 websites once .Net 5 is released?

原文 2019-09-24 11:05:39 3 1 .net/ .net-core/ .net-5

Following this question Is .NET Core ==.Net Framework 5?按照这个问题.NET Core ==.Net Framework 5 吗？

I am just about to make the colossal move to.Net Core 3 which means rewriting some very large applications from scratch.我即将大规模迁移到 .Net Core 3，这意味着从头开始重写一些非常大的应用程序。 I am at the most basic Hello World level on.Net Core 3 so don't want to start this massive migration if.Net 5 will be out next year and change everything again.我在 .Net Core 3 上处于最基本的 Hello World 级别，所以如果.Net 5 明年推出并再次改变一切，我不想开始大规模迁移。

If I start a project in.Net Core 3 today, am I going to have to change it again to work with.Net 5 going forward next year or will it just work in.Net 5?如果我今天在 .Net Core 3 中启动一个项目，我是否必须再次更改它才能在明年继续使用 .Net 5 还是只能在 .Net 5 中使用？

1 个解决方案

.NET 5 will be a logical successor to .NET Core 3.0, with the ecosystem aiming to merge multiple "stacks" (ASP.NET, Xamarin, WPF,..) into one platform and there was a marketing decision to drop the "Core" part of the name while not confusing it with the existing 4.* version of .NET Framework. .NET 5 will be a logical successor to .NET Core 3.0, with the ecosystem aiming to merge multiple "stacks" (ASP.NET, Xamarin, WPF,..) into one platform and there was a marketing decision to drop the "Core" part名称，同时不会将其与现有的 4.* 版本的 .NET 框架混淆。

If you migrate an application to .NET Core 3.0, you are set up good for .NET 5/6/+.如果您将应用程序迁移到 .NET Core 3.0，则您已为 .NET 5/6/+ 做好了准备。

Also note that .NET Core 3.1 - scheduled for November 2019 - is going to be a long-term support (LTS) release that will be supported with patches for at least 3 years.另请注意，.NET Core 3.1 - 计划于 2019 年 11 月发布 - 将是一个长期支持 (LTS) 版本，补丁支持至少 3 年。

There may or may not be breaking changes between .NET Core 3.0 and .NET 5, since it is a major version bump, but the migration cost will not be as huge as moving from classic ASP.NET to ASP.NET Core. There may or may not be breaking changes between .NET Core 3.0 and .NET 5, since it is a major version bump, but the migration cost will not be as huge as moving from classic ASP.NET to ASP.NET Core.