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
We are planning to upgrade the project from .NET Framework 4.5.2 (which reached its end of life on April 16th 2022) to .NET Framework 4.7.2. To ensure compatibility and provide time for users to transition, we will be releasing two versions of the project for at least this coming release, version 3.3.0.0.
.NET Framework 4.5.2 is no longer supported by Microsoft, meaning it no longer receives security updates or bug fixes. This could introduce security and stability risks if we continue to use it.
What We Need from You
We'd love your feedback on the following:
Are there any blockers or concerns you foresee with the move to .NET Framework 4.7.2?
Are you currently dependent on .NET Framework 4.5.2 (or older)? If so, how long do you expect to need this compatibility?
Any issues or bugs you've encountered during testing with the .NET 4.7.2 version?
Next Steps
We will release the next version, version 3.3.0.0, with binaries targeting both .NET Framework 4.5.2 and 4.7.2.
Depending on the feedback we receive, we may consider extending support for the .NET 4.5.2 version if necessary.
Please share any thoughts, issues, or suggestions in the comments below. Your feedback is valuable in ensuring this transition is as smooth as possible.
Thank you!
The text was updated successfully, but these errors were encountered:
Summary
We are planning to upgrade the project from .NET Framework 4.5.2 (which reached its end of life on April 16th 2022) to .NET Framework 4.7.2. To ensure compatibility and provide time for users to transition, we will be releasing two versions of the project for at least this coming release, version 3.3.0.0.
PingCastle_3.3.0-net452.zip, targeting .NET Framework 4.5.2.
PingCastle_3.3.0-net472.zip, targeting .NET Framework 4.7.2.
Why This Change?
.NET Framework 4.5.2 is no longer supported by Microsoft, meaning it no longer receives security updates or bug fixes. This could introduce security and stability risks if we continue to use it.
What We Need from You
We'd love your feedback on the following:
Next Steps
Please share any thoughts, issues, or suggestions in the comments below. Your feedback is valuable in ensuring this transition is as smooth as possible.
Thank you!
The text was updated successfully, but these errors were encountered: