WSB Guardian (English)

WSB Guardian 1.1.3.2224

This update contains the following improvements:

  • Numerous improvements to the FileGuard module, including prevention of case sensitivity of extensions and more selective notifications.
  • The lay-out of the input fields on the DynalogPlus window is optimized.

This update also solves 2 issues:

  • An issue whereby a file couldn’t be moved as it already existed on the target location.
  • An issue whereby changing the Dynalog option didn’t seemed to be accepted.

WSB Guardian 1.1.0.2171

New features

FileGuard

A proactive way to let WSB Guardian proactively check changed files in certain directories. By default new files – certain file types – in the downloads directory will automatically be checked.

DynalogPlus

A brand new tracking engine to monitor the application. This engine remplaces the previous tracking module, but runs independently from (and may not be confused with) the regular Dynalog module.

Other new features

  • The library is loaded more targetted.
  • The number of active threads en status of FileGuard is now shown on the monitoring dashboard.

Improvements

  • Smarter consultation of definitions
  • Performance improvements for monitoring
  • Updated list of providers
  • Numerous improvements to the analysis module
  • Certain translations are optimized
  • WSB Glorian is updated to version 1.8.2.0
  • SharpZipLib is updated to version 1.2.0
  • RestSharp is updated to version 106.6.10
  • KnownFolders added, version 1.2.1

Solved bugs

  • An error was thrown when a certain string was too long.
  • Fixed an access problem in the tracking and history module.
  • An analysis couldn’t be finished when a consolidation task started simultaneously.
  • Consulting the library resulted in a never ending loop.

WSB Guardian 1.0.4.1129

Resolved issues

  • The scan wasn’t resumed by the runtime module in a next program session.
  • The loading of the library fails when a file no longer exists.

New

  • The session / process id is now available in certain history overviews. By default this column is hidden.
  • It’s possible to hide / show columns in the history overview by clicking right on the column headers, a context menu will become visible.

Improved

  • The tracking module is fed from more procedures.
  • The tracking module is improved to prevent an “in use” error from bein thrown.
  • The French language file contained some unintended English translations.
  • Some improvements were made in the runtime module.

WSB Guardian 1.0.3.1082

This version contains the following improvements:

  • WSB Glorian shows the right version number again.
  • Optimization of certain translations and labels for improved readability.
  • Improvements on the library, defragmentation and analysis.
  • Introduction of tracking-logs in the scan engine to support finding errors, including the automatic removal of these logs after 60 days. (The longs aren’t shared.)

WSB Guardian 1.0.1.1026

New in this version:

  • Message when your version is no longer supported and have to be updated.
  • The startpage of the settings has a new tile lay-out. Two new categories were added: monitoring & maintenance.
  • Possibility to see all available datasets and to delete unused ones.
  • Possibility to get a detailed overview of all available definitions (through ‘about WSB Guardian’).

Improved in this version:

  • The version and indicative numbers of the definitions on the ‘about WSB Guardian’ page are more reliable starting of this version.
  • Optimization of the location of certain settings.
  • The numbers on the monitoring dashboard are refreshed every second.
  • Optimization of the code for improved security.
  • Optimization of the consultation and update of the definitions.
  • The dynamic error logging is improved.
  • Improvement on the runtime engine.

Solved problems:

  • Consultation of the definitions could result in an error.
  • Loading of new definitions could result in an error.
  • The removal of a dataset file was impossible due to a lack of privilages.
  • Resuming a finished scan could result in an error.
  • Loading an empty runtime file could result in an error.

WSB Guardian 1.0.0.990

This update contains a lot of new features and improvements, so does it means the end of the bèta stage. WSB Guardian is now officially ready for use on larger scale and better than ever before.

Memory usage

60% less memory usage

Based on our internal tests, memory usages has decreased with about 60%. In certain cases a decrease of up to 80% was noticed. In numbers this means memory usage is now about 80 to 180 MB instead of 400 to 500 MB.
  • Improved Releasing unused memory
  • Improved Closing unused read and write streams

Scan-engine

  • New Defragmentation of datasets
  • New Central cancellation system
  • New Cloud scanning for analysis
  • New Advanced methode for deleting (obsolete) datasets
  • Improved Removing datasets
  • Improved Naming of datasets

Definitions

  • New Selective loading and reloading of definitions
  • New Dump unused definitions
  • Improved Consolidation of local and global definitions (cf. defragmentation and smart consolidation)
  • Improved Removal of code which was responsible for a reload of the definitions on closure of the application
  • Improved Smarter consultation of definitions
  • Improved Connection to server
  • Improved Way on which definitions are consulted

Monitoring

  • New Dashboard of core parameters of application (ex. memory usage)

Dynalog

What is Dynalog?

Dynalog is a system which enables the application to create an overview of what it does to support the developers in finding high memory usage processes, errors in the code and other problems.
  • Improved System to register activities
  • Improved System to save reports
  • Improved Overview of generic parameters
  • New Report and settings for each user
  • New Option to share reports, including information to comply with GDPR regulation

Updated components

  • WpfAnimated gif 1.4.18
  • Restsharp 106.6.9
  • SharpZipLib 1.1.0
  • WSB Glorian 1.8.0.0

General

  • Improved Removal or deactivation of unused code
  • Improved Error handling
  • Improved Avoiding null-exceptions (cf. lack of results)

And a lof of other small improvements, bug fixes and more!

Important sidenote

Please note that the decrease in memory usage might only be noticable after a while. We estimate it can take up to 60 days before you enjoy the true benefits of our optimizations. However, by cancelling your active scan and starting a new one, you can speed up things a lot. Only scans indexed by this release or newer will enjoy the benefits.

Our server definitions are optimized since May 2019 and your local definitions will be after the next consolidation processes. Consolidation is done at weekly (limited) and monthly (full) frequency. After maximum 30 days your definitions should be 100% optimized.

Scroll to top