docs icon indicating copy to clipboard operation
docs copied to clipboard

.Net 4 is missing

Open cadop opened this issue 3 years ago • 4 comments

I assume there is some reason that is obvious to regular users, but there is an explanation for .NET 7.x, 6.x, 5.x, and 3.x, but skips 4.x .

In the text:

C# 11 is supported only on .NET 7 and newer versions. C# 10 is supported only on .NET 6 and newer versions. C# 9 is supported only on .NET 5 and newer versions. C# 8.0 is supported only on .NET Core 3.x and newer versions.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

cadop avatar Jul 22 '22 15:07 cadop

Very short version of the history of .NET.

It started as .NET, which evolved up to .NET 4. Then started .NET Core, evolved up to .NET Core 3.1. After .NET Core 3.1 there was a desire to drop "Core" for moving on the future solely as .NET.

As there was already a .NET 4 this version couldn't be used again, so there was a jump forward to .NET 5.

For more infos please see .NET Core is the Future of .NET and the linked posts.

gfoidl avatar Jul 25 '22 13:07 gfoidl

I see. I'm not sure how to fix the phrasing, but I think the confusing part is core vs framework.

image

The heading says framework, and when I am building my project i need to set .net framework, so its hard to find information on this framework targeting pack because these links (referenced in the issue) keep showing up.

image

cadop avatar Jul 25 '22 13:07 cadop

ping @richlander

Do you have good wording to disambiguate between "target framework" and ".NET Framework"?

BillWagner avatar Jul 28 '22 13:07 BillWagner

We don't. However, in that table, the column header could be simplified to just "Target" or "Target platform". Target frameworks always include a version, so the column technically isn't a target framework, but something more abstract. There is a name for that concept, too, but that's adding more complexity.

richlander avatar Jul 30 '22 18:07 richlander