Update compatibility message for trying to target net10.0 in 17.14

[marcpopMSFT]

Using the 10.0.1xx SDK to target net10.0 is not supported unless you're using VS 18.0.0. We update this code and message every year.

For this year

• update the message to say targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported
• update to a new NETSDK message number and move it to the end of the resx file
• Update the id for the message to be accurate
• Update the latest message added comment
• Update the defaultItems.targets logic with a new target name, the new warning ID, and the correct versions

https://github.com/dotnet/sdk/blob/release/10.0.1xx/src/Tasks/Microsoft.NET.Build.Tasks/targets/Microsoft.NET.Sdk.DefaultItems.targets#L141

https://github.com/dotnet/sdk/blob/release/10.0.1xx/src/Tasks/Common/Resources/Strings.resx#L973

[alexey-leonovich]

@marcpopMSFT I'm confused by #50749 description:

1. The warning will now appear when users attempt to build projects with: MSBuild version < 17.14.0 AND Targeting .NETCoreApp AND Target framework version >= 10.0 means that .NET 10.0 development IS supported in Visual Studio 2022 17.14.x. _WarnWhenUsingNET10AndVSPriorTo1714 has the same meaning.
2. Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported evidentially means that .NET 10.0 development IS NOT supported in Visual Studio 2022 17.14.x.

So what is the plan? Will it be possible to target .NET 10 in Visual Studio 2022? Or Visual Studio 2026 will be mandatory?

[cremor]

@alexey-leonovich That PR description was written by AI. I'd say it is clarly wrong. It even contradicts itself, because at the very top it says "Visual Studio 2022 17.14 or earlier versions." while at the bottom it says "MSBuild version < 17.14.0".

[marcpopMSFT]

I think the message and logic are fixed now. Targeting net10 will require VS 2026 as there are matching IDE side changes. This is a warning only as not every scenario is impacted so some customers may be successful using VS 2022 but we won't be testing with that configuration and we know not all scenarios will work.

[alexey-leonovich]

we know not all scenarios will work.

Could you please elaborate which specific scenarios are known to be broken?

[MagicAndre1981]

Targeting net10 will require VS 2026 as there are matching IDE side changes.

which changes in detail are required/made compared to 17.14 that only VS2026 can work? VS2026 is not intended as production system so the only VS version we can use is VS2022.

[panxn]

Hello, do you know which VS version will .NET10 require? I'm referring to the November official release.
VS2022 17.14, or VS2026?

[balachir]

@marcpopMSFT I believe all pending work for 10.0 GA related to this issue has been completed. @NicoleWang001 has verified the fix too -- see comments here.

Can this issue be closed?