Another issue like #49 , some thrown exceptions aren't being caught by the bug report generator. More work is needed in that area.
In addition, certain Synology NUT servers allow a client to LOGIN successfully, but will then reply ACCESS-DENIED to a LOGOUT command. I don't think this should be happening, but regardless, we're not catching a protocol exception and allowing it to crash the program. Need to make sure we're handling protocol exceptions appropriately.
Summary of changes
More reorganization in WinNUT_Globals.vb. Renaming some variables for clarity.
Updated dependencies
Refactor error report generation. Attempts to account for more error conditions and ensure a report can be generated.
Various improvements to protocol code, focusing on the Login subroutine.
Additional small tweaks to error report generation; corrected output formatting and try to standardize times and locale.
Additional compatibility with Synology NUT server quirk when the client is not in the allowed clients list (Synology-only feature)
Per #79 and #80:
Another issue like #49 , some thrown exceptions aren't being caught by the bug report generator. More work is needed in that area.
In addition,
certainSynology NUT servers allow a client to LOGIN successfully, but will then reply ACCESS-DENIED to a LOGOUT command. I don't think this should be happening, but regardless, we're not catching a protocol exception and allowing it to crash the program. Need to make sure we're handling protocol exceptions appropriately.Summary of changes