-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Support CsWinRT 3.0 multi-targeting and WindowsSdkPackageMinimumRevision #50264
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
1fa8f16
2ad9302
c256006
4821072
aa2210e
ba90d36
a6e227a
4d465e6
676ece8
0c68835
58c260c
d8d8cb0
fd4f274
983f973
0e83d36
b38c092
b622290
c29c79e
415c772
d7126cc
93d669f
ca298da
95fdd4b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1317,7 +1317,20 @@ Copyright (c) .NET Foundation. All rights reserved. | |
TargetingPackVersion="$(NETStandardLibraryRefPackageVersion)" | ||
/> | ||
<!-- Supported Windows versions --> | ||
<!-- | ||
Supported Windows versions using CsWinRT 3.0 (.NET 10 is the baseline). This leverages the revision of | ||
the Windows SDK version to allow multi-targeting, which is required to allow customers to gradually migrate. | ||
Both CsWinRT 3.0 and 2.x will be supported for a period of time, and packages can target both of them. | ||
--> | ||
<WindowsSdkSupportedTargetPlatformVersion Include="10.0.26100.1" WindowsSdkPackageVersion="$(MicrosoftWindowsSDKNETRef10_0_26100PackageVersion)" MinimumNETVersion="10.0" /> | ||
<WindowsSdkSupportedTargetPlatformVersion Include="10.0.22621.1" WindowsSdkPackageVersion="$(MicrosoftWindowsSDKNETRef10_0_22621PackageVersion)" MinimumNETVersion="10.0" /> | ||
<WindowsSdkSupportedTargetPlatformVersion Include="10.0.22000.1" WindowsSdkPackageVersion="$(MicrosoftWindowsSDKNETRef10_0_22000PackageVersion)" MinimumNETVersion="10.0" /> | ||
<WindowsSdkSupportedTargetPlatformVersion Include="10.0.20348.1" WindowsSdkPackageVersion="$(MicrosoftWindowsSDKNETRef10_0_20348PackageVersion)" MinimumNETVersion="10.0" /> | ||
<WindowsSdkSupportedTargetPlatformVersion Include="10.0.19041.1" WindowsSdkPackageVersion="$(MicrosoftWindowsSDKNETRef10_0_19041PackageVersion)" MinimumNETVersion="10.0" /> | ||
<WindowsSdkSupportedTargetPlatformVersion Include="10.0.18362.1" WindowsSdkPackageVersion="$(MicrosoftWindowsSDKNETRef10_0_18362PackageVersion)" MinimumNETVersion="10.0" /> | ||
<WindowsSdkSupportedTargetPlatformVersion Include="10.0.17763.1" WindowsSdkPackageVersion="$(MicrosoftWindowsSDKNETRef10_0_17763PackageVersion)" MinimumNETVersion="10.0" /> | ||
<!-- Supported Windows versions using CsWinRT 2.x --> | ||
Comment on lines
+1320
to
+1333
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should we also delete the old items for .NET 5 and 6 below? Since they're out of support now? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I feel like in the past I have ran into scenarios where folks like VS were still relying on them as part of their tests. So I wouldn't want to clean it up as part of this change. |
||
<WindowsSdkSupportedTargetPlatformVersion Include="10.0.26100.0" WindowsSdkPackageVersion="$(MicrosoftWindowsSDKNETRef10_0_26100PackageVersion)" MinimumNETVersion="8.0" /> | ||
<WindowsSdkSupportedTargetPlatformVersion Include="10.0.22621.0" WindowsSdkPackageVersion="$(MicrosoftWindowsSDKNETRef10_0_22621PackageVersion)" MinimumNETVersion="8.0" /> | ||
<WindowsSdkSupportedTargetPlatformVersion Include="10.0.22000.0" WindowsSdkPackageVersion="$(MicrosoftWindowsSDKNETRef10_0_22000PackageVersion)" MinimumNETVersion="8.0" /> | ||
|
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We probably need to undo this too, if we're going to use the same package for .NET 9 and 10?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I put separate items here because these are linked to the TargetPlatformVersion, so we need items both for the .0 and .1 versions. The actual package versions are the same between the corresponding items.
It would be possible to do this differently, but this seemed to be the simplest to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, gotcha, yeah makes perfect sense! Thank you for the additional context. Perhaps we could add a line to that comment at line 1321 to also mention this, for future reference? In case anyone else wonders the same I mean.