Bot releases are visible (Hide)

WinNUT-Client - v2.3.8988 Latest Release

Published by gbakeman 2 months ago

What's Changed

Update Overhaul Part 1 - Octokit Library in https://github.com/nutdotnet/WinNUT-Client/pull/176
- WinNUT updater code overhauled in anticipation of further changes in WinNUT. The Updater GUI looks and functions the same for the most part. In need of translations (although you may want to wait for the next part of this update before making translations.)
- Added a third party library (Octokit) in favor of custom update query code.
- Removed the Auto update option since WinNUT doesn't have the functionality to check for an update periodically during operation, it can only check at startup under a different option. See #175 for more info.
- Please keep in mind that the impacts of these changes won't be completely in force until the following update. I've tested this a few times on my own computer, but the ultimate test won't be until later.

Build automation

Modify MSBuild command, version upgrades in https://github.com/nutdotnet/WinNUT-Client/pull/178

Full Changelog: https://github.com/nutdotnet/WinNUT-Client/compare/v2.3.8981...v2.3.8988

WinNUT-Client - v2.3.8981

Published by gbakeman 3 months ago

What's Changed

Persistent Connection attempts, quieter notifications in https://github.com/nutdotnet/WinNUT-Client/pull/171
- Slightly changes the Connection menu in WinNUT. Added some icons, as well as a toggle for keeping a persistent connection (connects with the Auto Reconnect option in the Preferences menu)
- WinNUT now attempts to keep a connection indefinitely. There should be less notification spam as well.

Full Changelog: https://github.com/nutdotnet/WinNUT-Client/compare/v2.3.8970...v2.3.8981

WinNUT-Client - v2.3.8970

Published by gbakeman 3 months ago

Sorry about the broken installer if you were able to download it in the last pre-release. That led me to deploy an update in AGauge which not only fixed that, but another older bug as well. I guess I can't blame this one on CrowdStrike. 😅

What's Changed

Separate AGauge into a NuGet package, with inherited control in https://github.com/nutdotnet/WinNUT-Client/pull/59
locale: add Ukrainian language by @Vladdrako in https://github.com/nutdotnet/WinNUT-Client/pull/160
More efficient connection handling, better suspend/resume support in https://github.com/nutdotnet/WinNUT-Client/pull/163
- Better tolerance of NUT servers behaving strangely (s/o to Synology)
- Login command now works correctly, and is not critical for connecting to your UPS. Try deleting your username and password and see if everything still works.
- Official support for network protocol version 1.3
- Polling interval is no longer ignored (always defaulted to 3.0 seconds)
Revert Polling Interval display to seconds in https://github.com/nutdotnet/WinNUT-Client/pull/164
AGauge - fix tick mark bug in https://github.com/nutdotnet/WinNUT-Client/pull/168
- Also fixes the broken installer in #167.

New Contributors

@Vladdrako made their first contribution in https://github.com/nutdotnet/WinNUT-Client/pull/160

Full Changelog: https://github.com/nutdotnet/WinNUT-Client/compare/v2.3.8892...v2.3.8970

WinNUT-Client - Pre-Release v2.3.8892

Published by gbakeman 6 months ago

What's Changed

Power value calculation updates (specifically for Huawei UPS) by @gbakeman in https://github.com/nutdotnet/WinNUT-Client/pull/151
Update zh-cn language and add UPS States flag by @MaxMadcc in https://github.com/nutdotnet/WinNUT-Client/pull/152

Full Changelog: https://github.com/nutdotnet/WinNUT-Client/compare/v2.3.8883...v2.3.8892

WinNUT-Client - Pre-Release v2.3.8883

Published by gbakeman 6 months ago

What's Changed

Fix 'Create LogFile' option is on, but the option is not working when program is running. by @MaxMadcc in https://github.com/nutdotnet/WinNUT-Client/pull/147

Full Changelog: https://github.com/nutdotnet/WinNUT-Client/compare/v2.2.8834...v2.3.8883

WinNUT-Client - Pre-Release v2.3.8834

Published by gbakeman 8 months ago

What's Changed

Fixed the bug where the UPS using battery power was not displayed. by @MaxMadcc in https://github.com/nutdotnet/WinNUT-Client/pull/137
⚠️ Fix Application Settings not carrying over on upgrade/update in https://github.com/nutdotnet/WinNUT-Client/pull/140

New Contributors

@MaxMadcc made their first contribution in https://github.com/nutdotnet/WinNUT-Client/pull/137

Full Changelog: https://github.com/nutdotnet/WinNUT-Client/compare/v2.3.8824...v2.3.8834

WinNUT-Client - Pre-Release v2.3.8824

Published by gbakeman 8 months ago

What's Changed

Several bugfixes for when the NUT server is reporting unexpected, out-of-range values (see also https://github.com/nutdotnet/WinNUT-Client/pull/131). In addition;

Fixed an issue where log file controls were enabled when logging was not enabled, and the log file was not present
Fixed being unable to change update interval value, reinforced units as milliseconds throughout the program
Fixed WinNUT titlebar being blank
The Import Old Preferences File menu item now enables and disables correctly
UPS variables now default to an obvious out of range value (-1) to indicate that there was a problem retrieving them. I don't have an optimal solution for handling missing variables implemented yet; see https://github.com/nutdotnet/WinNUT-Client/issues/116 for more info
Battery charge and run time value calculations will also now correctly fail if there are any missing variables required for the calculations

Full Changelog: https://github.com/nutdotnet/WinNUT-Client/compare/v2.3.8800...v2.3.8824

WinNUT-Client - Pre-Release v2.3.8800

Published by gbakeman 9 months ago

⚠️ Warning: Important changes to WinNUT preferences system

WinNUT has undergone a fairly important change to its underlying preferences system, that besides an import dialog, should be otherwise unnoticeable.

WinNUT used to store its settings in the User Registry Hive. This was problematic for a number of reasons; the largest one being that I'm moving WinNUT to a new deployment system which would be helped by migrating to the default .NET Framework settings system.

I've created a migration wizard which will pop up the first time you open this version of WinNUT. It will ask you what you would like to do with the old settings; Import, Backup (save a copy), Delete, or do nothing and use a fresh copy of the Settings. Besides the Delete option, this process is entirely non-destructive and will leave your old preferences as they were in the Registry. As long as an old copy of WinNUT preferences remain in the Registry, there will always be an option in the File menu that will restart the migration wizard. I've tested this several times on my own system, and everything appears to be working as intended. Please comment in the Discussion if you experience any problems, or have any questions.

WinNUT 1.x Import procedure

Up until this release, WinNUT used to have an option for importing WinNUT 1.x settings into its Preferences registry system. I removed this feature as of now since I believe most people are currently running WinNUT 2. If you have WinNUT 1.x settings that you wish to carry over, you may then download the release prior to this one, launch it, run the 1.x import procedure, exit, then update to this version and follow the migration wizard as previously described.

🌐 Translators needed!

If you are proficient at translating from English to another language, please consider contributing a translation to this project. Several new strings have been added, while existing ones need review. It's a great way to contribute back to this project and benefit other users.

What's Changed

Upgrade to .NET Framework Settings System by @gbakeman in https://github.com/nutdotnet/WinNUT-Client/pull/114

Full Changelog: https://github.com/nutdotnet/WinNUT-Client/compare/v2.3.8754...v2.3.8800

WinNUT-Client - Pre-Release v2.3.8754

Published by gbakeman 10 months ago

First pre-release of the 2.3 cycle.

What's Changed

Correct FormatException when parsing Invariant-locale numbers in user's locale by @gbakeman in https://github.com/nutdotnet/WinNUT-Client/pull/125
- This will fix immediate disconnects people were experiencing with non-en* locales.

Full Changelog: https://github.com/nutdotnet/WinNUT-Client/compare/v2.2.8719...v2.3.8754

WinNUT-Client - Release v2.2.8719

Published by gbakeman 11 months ago

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.

Windows 10 Hibernate & Clear Shutdown Timer (redo) in https://github.com/nutdotnet/WinNUT-Client/pull/7
Improve Connection handling & Logging, Power State handling in https://github.com/nutdotnet/WinNUT-Client/pull/11
Better disconnection handling in main form in https://github.com/nutdotnet/WinNUT-Client/pull/20
Large changes to Socket/UPS, DATA-STALE error handling in https://github.com/nutdotnet/WinNUT-Client/pull/25
Battery-related changes in https://github.com/nutdotnet/WinNUT-Client/pull/33
Re-activate stop actions system and status updates overhau in https://github.com/nutdotnet/WinNUT-Client/pull/36
Correct Interval/Delay value in https://github.com/nutdotnet/WinNUT-Client/pull/37
Fix incorrect windows version detection in https://github.com/nutdotnet/WinNUT-Client/pull/51
Fix List_Var_Gui error in https://github.com/nutdotnet/WinNUT-Client/pull/52
Upgrade unhandled exception handling, cryptography in https://github.com/nutdotnet/WinNUT-Client/pull/49
Respect Follow FSD setting in https://github.com/nutdotnet/WinNUT-Client/pull/57
Improve connection loss handling in https://github.com/nutdotnet/WinNUT-Client/pull/64
Define UPS_States values as pow of 2 to fix state change detection by @supersmile2009 in https://github.com/nutdotnet/WinNUT-Client/pull/71
Improvements to Login subroutine in https://github.com/nutdotnet/WinNUT-Client/pull/88
Error Reporting & Exception Catching Refactor in https://github.com/nutdotnet/WinNUT-Client/pull/86
Fix FormatException in Update_Gui in https://github.com/nutdotnet/WinNUT-Client/pull/98
Fix unable to exit with tray closing functionality in https://github.com/nutdotnet/WinNUT-Client/pull/108
Re-enable retry connection on first start in https://github.com/nutdotnet/WinNUT-Client/pull/107
Correct UPS Load display in https://github.com/nutdotnet/WinNUT-Client/pull/112

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.

Creating Continuous Integration workflow in https://github.com/nutdotnet/WinNUT-Client/pull/28
Installer dependency cleanup in https://github.com/nutdotnet/WinNUT-Client/pull/48
Upgrade to .Net Framework 4.8 in https://github.com/nutdotnet/WinNUT-Client/pull/53
Fix release build by @supersmile2009 in https://github.com/nutdotnet/WinNUT-Client/pull/72
Update README.md by @pvanderp in https://github.com/nutdotnet/WinNUT-Client/pull/87

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.

Logging Improvements in https://github.com/nutdotnet/WinNUT-Client/pull/10
Additional logging improvements and cleanup in https://github.com/nutdotnet/WinNUT-Client/pull/19
Logging fixes in https://github.com/nutdotnet/WinNUT-Client/pull/50
Attempting to finally solve data directory oddities in https://github.com/nutdotnet/WinNUT-Client/pull/62
Fix logs going to App directory again in https://github.com/nutdotnet/WinNUT-Client/pull/111

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.

Improve de-DE (German) Translation in https://github.com/nutdotnet/WinNUT-Client/pull/8
Add Translation/zh-TW/zh-TW.csv for Chinese (Traditional) by @yrctw in https://github.com/nutdotnet/WinNUT-Client/pull/23
Small updates to german Translation by @MartinKurtz in https://github.com/nutdotnet/WinNUT-Client/pull/30
Applying translations in https://github.com/nutdotnet/WinNUT-Client/pull/39
Update translation for Traditional Chinese by @yrctw in https://github.com/nutdotnet/WinNUT-Client/pull/119

New Contributors

@yrctw made their first contribution in https://github.com/nutdotnet/WinNUT-Client/pull/23
@MartinKurtz made their first contribution in https://github.com/nutdotnet/WinNUT-Client/pull/30
@andriibratanin made their first contribution in https://github.com/nutdotnet/WinNUT-Client/pull/54
@supersmile2009 made their first contribution in https://github.com/nutdotnet/WinNUT-Client/pull/71
@pvanderp made their first contribution in https://github.com/nutdotnet/WinNUT-Client/pull/87

Full Changelog: https://github.com/nutdotnet/WinNUT-Client/compare/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.

WinNUT-Client - Pre-Release v2.2.8693