Hope that the future can in Nuget package management page through the UI update Microsoft.Windows.SDK.NET.Ref package

[Gaoyifei1011]

Describe the bug

Hope that the future can in Nuget package management page through the UI update Microsoft.Windows.SDK.NET.Ref package
希望未来能在 Nuget 包管理页面中通过 UI 更新 Microsoft.Windows.SDK.NET.Ref 包

After updating to CsWinRT 2.1.X, we found that the Microsoft.Windows.SDK.NET.Ref framework package will also be updated with the version of CsWinRT, however if we want to know the latest version of Microsoft.Windows.SDK.NET.Ref, we need to manually search and modify the 10.0.26100.45 property value, which is no longer very convenient. I hope that the CsWinRT team can communicate with the Visual Studio team, and you can add a separate display of the content of the framework package on the Nuget package management page, and you can follow the ordinary Nuget package to update it on the Nuget package management page
在更新到 CsWinRT 2.1.X 后，我们发现Microsoft.Windows.SDK.NET.Ref 框架包也会随着 CsWinRT 的版本进行更新，然而如果我们想了解 Microsoft.Windows.SDK.NET.Ref 的最新版本，需要手动搜索并修改 csproj 下的 10.0.26100.45 属性值，这已操作不太方便。希望 CsWinRT 团队能和 Visual Studio 团队能沟通一下，可以在 Nuget 包的管理页面添加一个单独显示框架包的内容，可以跟随普通的 Nuget 包在 Nuget 包管理页面进行更新

To Reproduce

Expected behavior

Can add a separate display of the content of the framework package on the Nuget package management page, and you can follow the ordinary Nuget package to update it on the Nuget package management page
可以在 Nuget 包的管理页面添加一个单独显示框架包的内容，可以跟随普通的 Nuget 包在 Nuget 包管理页面进行更新

Version Info

CsWinRT 2.1.3
.NET 9 Preview 7
Windows SDK 10.0.26100.45
Visual Studio 17.11.3

Additional context

None

[dongle-the-gadget]

This is a .NET limitation, since you cannot directly reference a .NET SDK.

[Gaoyifei1011]

This is a .NET limitation, since you cannot directly reference a .NET SDK.

Thanks for the reminder, I've already raised this issue under the dotnet runtime. dotnet/sdk#43335
感谢提醒，我已经在 dotnet runtime 下提出这个问题了。dotnet/sdk#43335

[manodasanW]

Typically, the hope is you do not need to manually set WindowsSdkPackageVersion or worry about incrementing the version for it as it would automatically get updated via updates to the .NET SDK. But there are occasions like right now where there is a time period until the .NET SDK version comes out where it might need to be set. We will need to see how we can improve the experience when situations like these happens.

[Gaoyifei1011]

Typically, the hope is you do not need to manually set WindowsSdkPackageVersion or worry about incrementing the version for it as it would automatically get updated via updates to the .NET SDK. But there are occasions like right now where there is a time period until the .NET SDK version comes out where it might need to be set. We will need to see how we can improve the experience when situations like these happens.

At present, I see that every time a new version of CsWinRT is released, the Windows SDK version will also be updated, and before CsWinRT supported AOT, the Windows SDK version was updated less frequently. So in future releases, will the Windows SDK version always follow the CsWinRT update? If so, I find it cumbersome to search for the Windows SDK version and manually change the version number every time.
目前，我看到每一次 CsWinRT 发布新版本的时候，Windows SDK 版本也会随着更新，在 CsWinRT 支持 AOT 之前，Windows SDK 版本更新的并没有那么频繁。所以在之后的版本中，Windows SDK 版本一直会跟随 CsWinRT 更新吗？如果是的话，我觉得每一次需要搜索 Windows SDK 版本并手动修改版本号这个操作很麻烦。

[hez2010]

The sdk version will be bumped in future version of .NET SDK. It's not actionable on the CsWinRT side.