Allows plugins and core modules to store configuration data in System Ninja’s configuration file. Handles all data integrity checks and ensures that plugins cannot create superflous files.

When error logging is enabled, any log files more than two days old will be removed when System Ninja closes.

The new class can be initialized by plugin and provides accessor and mutator methods for most core functionality

Greater detail and depth is included in the error logs when debug mode is enabled. It’s now possible to determine which module, plugin or class generated an error to ease debugging.

Plugins can now directly write to the error log to assist with development.

It’s possible to identify installed programs based on a search phrase.

The list of installed programs is now a representation of a collection of InstalledProgram objects, rather than simply a list of data.

Previously, plugins would only be detected if their startup form was called ‘Form1.’ This limitation has been removed, allowing plugins to use thier assembly name as a primary form name instead.

Previously, the scan results list could only be sorted alphabetically. This meant that files could not be properly ordered by filesize, as the unit of measurement (eg KB, MB) would interfere with the Sort() method.

If the uninstaller referenced in the ‘UninstallString’ registry value does not exist, the FileNotFoundException is correctly handled.