Release v2.2.8719 and a hotfix #127
gbakeman
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
https://github.com/nutdotnet/WinNUT-Client/releases/tag/v2.2.8719
Introduction
After thirty-three months since the last release v2.0.7722.30975, with work by @gawindx, myself and several other contributors to the WinNUT project, I'm proud to offer the latest stable release of WinNUT. This marks the first stable release since @gawindx kicked off the effort to modularize WinNUT and improve maintainability and stability. Unfortunately we've lost contact with them, but I decided to take over and relocate the project in an effort to leave WinNUT in a stable and efficient state. I hope you find this release meeting your expectations and needs for UPS monitoring.
Functional/event handling improvements
Many functional changes under the hood have been made to WinNUT, starting with the code modularization kicked off by @gawindx. Further work was done to improve & fix handling power event changes, connection changes and other events from the UPS. Windows 10+ notifications should now be working, as well as the stop action system and Full Shut Down commands from the UPS. The Error Reporting system is more stable, and the automatic reconnection system is fully working. UPS Load calculation has also been reworked.
Setup and deployment
Work was done to change how WinNUT was deployed, from simple changes to the Setup project builder to the deployment of a debug Continuous Integration system for making debug builds automatically for pull requests. WinNUT was also upgraded to use the .NET Framework version 4.8. This is the latest version that still has Windows 7 SP1 as the minimum system requirement.
Logging improvements
How and where WinNUT stores log files has been standardized against the .NET Framework so they can be predictably found in
(user folder)\AppData\Roaming\NUTDotNet\WinNUT Client\(version)\Logs
.Translation improvements
Our international audience has been busy improving translations for WinNUT. A bug causing errors when strings were too long was fixed. If you see translations that need additional work, please consider contributing.
New Contributors
Full Changelog: v2.0.7722.30975...v2.2.8719
Addendum/Closing words
From the onset, I thought my efforts would be simply to fix bugs in WinNUT and leave it otherwise unchanged. Afterwards, I would begin work on WinNUT's replacement. As time goes on, I'm realizing that there's more work I'd like to do on WinNUT to leave it in the best possible state, as well as attempt to integrate the NUT.Net library I've been working on in preparation for the next version of WinNUT. Thus, I'm now planning on several more stable releases of WinNUT before I officially consider the project complete and deprecated. Please continue providing your feedback and bug reports so we can make this iteration of WinNUT the most complete and bug-free iteration yet.
Pre-Release v2.3.8754
First pre-release of the 2.3 cycle.
What's Changed
FormatException
when parsing Invariant-locale numbers in user's locale by @gbakeman in CorrectFormatException
when parsing Invariant-locale numbers in user's locale #125Full Changelog: v2.2.8719...v2.3.8754
Beta Was this translation helpful? Give feedback.
All reactions