You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to .NET Framework 4.6.1 reaching EoS, more and more packages (especially those published by Microsoft) are removing it from their supported targets, which results in issues for us when we want to update our own dependencies.
Continuing to use .NET 5 as our build SDK may result in security issues due to being at EoS, and it limits support for our test packages and other tools. Additionally .NET 6 supports the Apple M1 processor, meaning a better developer experience for any who may be using an M1 based machine.
What is the developer experience going to be?
Increasing the required SDK version will mean developers will need to install the newer SDK if not already installed, otherwise the experience will be unchanged.
Are there any security considerations?
If anything this will improve the security situation by enabling us to stay better up to date
What/Why
What are you proposing?
I propose removing the explicit
net461
target from our packages as .NET Framework 4.6.1 reached End of Support in April 2022, and additionally updating the SDK used to build the packages to .NET 6 as .NET 5 reached End of Support in May 2022.What problems are you trying to solve?
What is the developer experience going to be?
Are there any security considerations?
What is the user experience going to be?
Consumers of the library will only be impacted if they are specifically targeting .NET Framework 4.6.1, all other consumers (including those who have updated to .NET Framework 4.6.2 from 4.6.1) will be unaffected as all other recent versions of .NET Framework and .NET support .NET Standard 2.0 which we target.
Are there breaking changes to the User Experience?
As above regarding those on 4.6.1
Why should it be built? Any reason not to?
Enables continued modernisation and package updates of the client, resulting in better user experiences and improved security posture.
What will it take to execute?
Requires minimal effort, updating SDK version number in global.json and workflows, updating necessary packages, removing net461 target from projects.
Any remaining open questions?
The text was updated successfully, but these errors were encountered: