Fix TargetPlatformVersion normalization for Windows#29009
Fix TargetPlatformVersion normalization for Windows#29009dsplaisted merged 9 commits intodotnet:release/7.0.2xxfrom
Conversation
…013.4 Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.SignTool , Microsoft.DotNet.XUnitExtensions From Version 7.0.0-beta.22511.2 -> To Version 7.0.0-beta.22513.4
…014.3 Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.SignTool , Microsoft.DotNet.XUnitExtensions From Version 7.0.0-beta.22511.2 -> To Version 7.0.0-beta.22514.3
…031.4 Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.SignTool , Microsoft.DotNet.XUnitExtensions From Version 7.0.0-beta.22511.2 -> To Version 7.0.0-beta.22531.4
…107.1 Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.SignTool , Microsoft.DotNet.XUnitExtensions From Version 7.0.0-beta.22511.2 -> To Version 7.0.0-beta.22557.1
…108.4 Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.SignTool , Microsoft.DotNet.XUnitExtensions From Version 7.0.0-beta.22511.2 -> To Version 7.0.0-beta.22558.4
|
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
48d4e91 to
c610765
Compare
7e7930d to
b0d6e99
Compare
|
FYI @j0shuams |
This broke with changes related to dotnet#27199. It's now possible to have multiple supported platform version items for the same version.
Depending on whether we're using preview versions, some of the packages may be downloaded by NuGet and have lowercased names, while at other times they may be shipped in the packs folder and have mixed case.
b0d6e99 to
91b88f3
Compare
|
This was rejected for servicing as the customer impact is low to nonexistent, so I've re-targeted it to 7.0.2xx. |
|
@nagilson Care to review this so we can merge it now? |
There was a problem hiding this comment.
@dsplaisted I looked at the code and it seemed good, but I didn't see any test that tested this specific regression:
A TargetPlatformVersion property for Windows without a trailing “.0” won’t be normalized to 4 version sections anymore (for example from 10.0.18362 to 10.0.18362.0). Am I wrong that this is related to that?
The test changes I saw were just handling case-sensitivity, was a regression test added to check for the .0 behavior? I know some other tests (might) fail if it's wrong already.
|
Gotcha, thanks! |
This broke with #27199