Targeting net10.0-windows10.0.26100.1 triggers incorrect CsWinRT 3.x warning

[riverar]

Describe the bug

Creating a new C# project and targeting Windows 10.0.26100.1 results in strange warnings for frameworks not in use and unreleased.

C:\Program Files\dotnet\sdk\10.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Windows.targets(199,5): warning NETSDK1229: Targeting a Windows SDK version with '1' as the revision number will reference CsWinRT 3.0, which is currently in preview. The current project is targeting the Windows SDK version ''. If this is not intended, change the revision number to '0' to use CsWinRT 2.x instead.

To Reproduce

1. Create a new C# Console app
2. Target Windows / 10.0.26100.1
3. Build and observe warning

Project file:

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net10.0-windows10.0.26100.1</TargetFramework>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
  </PropertyGroup>

</Project>

Further technical details

details of dotnet --info

PS C:\Users\Rafael> dotnet --info .NET SDK: Version: 10.0.100 Commit: b0f34d51fc Workload version: 10.0.100-manifests.5fb86115 MSBuild version: 18.0.2+b0f34d51f

Runtime Environment:
OS Name: Windows
OS Version: 10.0.26220
OS Platform: Windows
RID: win-x64
Base Path: C:\Program Files\dotnet\sdk\10.0.100\

.NET workloads installed:
[maccatalyst]
Installation Source: VS 18.3.11218.70
Manifest Version: 26.1.10494/10.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\10.0.100\microsoft.net.sdk.maccatalyst\26.1.10494\WorkloadManifest.json
Install Type: Msi

[maui-windows]
Installation Source: VS 18.3.11218.70
Manifest Version: 10.0.0/10.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\10.0.100\microsoft.net.sdk.maui\10.0.0\WorkloadManifest.json
Install Type: Msi

[ios]
Installation Source: VS 18.3.11218.70
Manifest Version: 26.1.10494/10.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\10.0.100\microsoft.net.sdk.ios\26.1.10494\WorkloadManifest.json
Install Type: Msi

[android]
Installation Source: VS 18.3.11218.70
Manifest Version: 36.1.2/10.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\10.0.100\microsoft.net.sdk.android\36.1.2\WorkloadManifest.json
Install Type: Msi

Configured to use workload sets when installing new manifests.
No workload sets are installed. Run "dotnet workload restore" to install a workload set.

Host:
Version: 10.0.0
Architecture: x64
Commit: b0f34d51fc

.NET SDKs installed:
8.0.416 [C:\Program Files\dotnet\sdk]
10.0.100-rc.1.25451.107 [C:\Program Files\dotnet\sdk]
10.0.100 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 7.0.20 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 8.0.22 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 9.0.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 10.0.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 7.0.20 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 8.0.22 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 9.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 9.0.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 10.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 7.0.20 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 8.0.22 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 9.0.6 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 9.0.11 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 10.0.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
x86 [C:\Program Files (x86)\dotnet]
registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

Environment variables:
Not set

global.json file:
Not found

Learn more:
https://aka.ms/dotnet/info

Download .NET:
https://aka.ms/dotnet/download

Visual Studio 2016 Insiders 11218.70

[marcpopMSFT]

CC @Sergio0694

[Sergio0694]

This is basically the same as that internal ticket from last week. My understanding is that:

• The .1 TFMs showing up in the "target OS" dropdown are by design, and they're just temporarily not functional until we push a public preview for CsWinRT 3.0.
• The TFMs showing up under "minimum supported OS" are a bug and we should update VS to hide them there.

[catmanjan]

I tried this today, and I also got a compiler error:

The expression "[System.IO.Path]::GetDirectoryName('')" cannot be evaluated. The path is not of a legal form.

Referring to this line <_WinRTRuntimeDllDirectory>$([System.IO.Path]::GetDirectoryName('%(_WinRTRuntimeDllReferencePath.FullPath)'))</_WinRTRuntimeDllDirectory>

In the file "C:\Program Files\dotnet\sdk\10.0.202\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Windows.targets"

[Sergio0694]

Mmh not sure about this error. @catmanjan can you share a binlog? Also cc. @manodasanW.

"The TFMs showing up under "minimum supported OS" are a bug and we should update VS to hide them there."

Re: this, I'll try to figure out what change we need in VS and drive that.

[Sergio0694]

I've made a PR into the .NET project system to filter out the .1 TFMs from the "Supported OS version" dropdown, it should be available in Visual Studio and Visual Studio Code soon. The .1 TFMs in the "Target OS version" dropdown are by design, so I don't see anything else left here to address. @marcpopMSFT I don't have permissions in this repo, but we should resolve this 🙂

[marcpopMSFT]

@Sergio0694 sounds good. Can you link to the project system PR here so we have that connection?

[Sergio0694]

@marcpopMSFT the PR is into the internal repo, not on GitHub (I've been told the one on GitHub is an old mirror) 😅

[riverar]

[...] TFMs in the "Target OS version" dropdown are by design [...]

So are you saying the originally reported error is not fixed and we're just giving up on that?

[Sergio0694]

There's nothing to fix, that's by design. It's just temporarily inconvenient because CsWinRT 3.0 isn't released yet. But we can't really update everything exactly at the same time, there's half a dozen of components involved, each with its own release schedule 🥲

[marcpopMSFT]

Thanks. Agreed that we typically don't link to internal repos from here. Make sure there is a link to this issue from the internal repo though.

As for what's design or not, I believe you're saying that from the SDK perspective, it's expected that the .1 versions are available but temporarily, you're going to hide them from the dropdown until cswinrt3 is ready for broader consumption. So we are going to take action on this report, just not fixing the .1 versions to work just yet.