1. Minor cumulative additions
2. Fatal null reference exception handling changes

1. Minor cumulative additions
2. Placed open file methods in their own thread
3. Placed save file methods in their own thread

1. Minor cumulative additions
2. Dependency updates
3. Separated .NET Framework and .NET Standard libraries to reflect their constituent components

1. Minor cumulative changes applied
2. Dependencies updated
3. Reverted to Semantic Versioning (SemVer - ie major.minor.patch) notation

  The Ratcliff/Obershelp pattern-matching algorithm was developed by John W. Ratcliff and
  John A. Obershelp in 1983 to address concerns about educational software (Ratcliff, 1988).

  The Levenshtein distance is a string metric for measuring the difference between two
  sequences. The Levenshtein distance between two words is the minimum number of single-
  character edits (i.e. insertions, deletions or substitutions) required to change one
  word into the other.

  The Hamming Distance measures the minimum number of substitutions required to change
  one string into the other. The Hamming distance between two strings of equal length
  is the number of positions at which the corresponding symbols are different.

  A phonetic algorithm is a method for comparing strings by sound, specifically as
  pronounced in English, where differences in spelling can be overlooked.

 A short summary of the syntax used to call the Similarity application from the
 command line, providing a means to invoke a wide variety of options available
 in the GUI.

 You've gotta love a good cipher methodology.

  This has enabled us to significantly reduce the time required for a typical application
  initialisation.

  Background debug trace markers have been added to the pre-production and dev
  environment to monitor seek and process time intervals, particularly related to cloud
  server activity. This code is ignored by the compiler on release.

  It was noted that timeout errors (commonly 258, 165, 298 and -2 et al SQL and .NET
  timeouts) occurred during specific periods during the day.  This in turn brought to
  attention the need to invoke some background processes at different intervals during
  initialisation.

  In addition, these delays enabled us to accurately target retry attempts on stored
  procedures that we now knew did not experience a fatal error, which was a bonus.

  Enabled runtime error logging as a semi-permanent feature. It is now a user-defined
  option whose default is set to log to the cloud and works quietly in the background.
  Logging to file and to the console remain, but are disabled in production.