-
Notifications
You must be signed in to change notification settings - Fork 493
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
Remove out-of-support targets from test matrix #2976
Conversation
Need to update the supported platforms file, and probably the migraiton guide. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines failed to run 1 pipeline(s). |
6d6b6ff
to
a3eff77
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
a3eff77
to
7f344f5
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Double check on the variable for 3.1 which we are removing.
/azp run |
Azure Pipelines failed to run 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
supported_platforms.md
Outdated
@@ -20,6 +20,8 @@ Nightly test platform details: | |||
.NET versions tested on | |||
- .NET 7.0 | |||
- .NET 6.0 | |||
- .NET Core 3.1 | |||
- .NET Framework 4.6.1 (only IoT Hub SDKs) |
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.
Why only Hub SDKs? Is net461 not .netstandard2.0 compliant?
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.
net461 isn't fully compliant with ns2.0. For this reason I think we should test against net472 instead (which is what we have been doing). What do you think? @drwill-ms
From https://learn.microsoft.com/en-us/dotnet/standard/net-standard?tabs=net-standard-2-0#select-net-standard-version:
The versions listed here represent the rules that NuGet uses to determine whether a given .NET Standard library is applicable. While NuGet considers .NET Framework 4.6.1 as supporting .NET Standard 1.5 through 2.0, there are several issues with consuming .NET Standard libraries that were built for those versions from .NET Framework 4.6.1 projects. For .NET Framework projects that need to use such libraries, we recommend that you upgrade the project to target .NET Framework 4.7.2 or higher.
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.
Wow, I wonder why track2 tests with it then.
I'd say stick with 472 for now, but ask the azure sdk team about it.
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
* Remove out-of-support targets from test matrix (#2976) * Update supported_platforms.md Co-authored-by: David R. Williamson <drwill@microsoft.com> * Update supported_platforms.md Co-authored-by: David R. Williamson <drwill@microsoft.com> Co-authored-by: David R. Williamson <drwill@microsoft.com>
With this new version we can update out test matrix to only test against supported targets. Targets that have reached EOL will no longer be tested against.
Support matrix: https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core
Note: .NET 3.1 is also set to reach EOL in Dec 22. Should we remove this target from our testing matrix?