Fixes #72

Refers to #20

Refers to #20

Refers to #20

Refers to #20

Refers to #20

Fixes #51

Refers to #35

This introduces a new optional configuration parameter called
"LogLevelMonitoring" to adjust the log level of those messages related
to the load monitoring of the service.

Fixes #50

This prevents at least the log file from being cluttered up completely
in "normal" operation. As stated in #50 the level for those messages
should be configurable to allow for easy adjustments without the need to
recompile the service itself.

Fixes #38

Since we're now back on using a central location for storing temporary
transfer files, it does make sense again to check for that location to
exist on service startup (refers to #16).

This reverts commit 10640754.

Refers to #16

The name reflects the functionality much better.

Since this is not a common (central) location any more, it doesn't make
sense to check for it during startup or similar situations.

Megabytes have shown to be a bit clumsy in the configuration files, so
simply switch to the more useful Gigabytes unit.

Fixes #39

Allow setting the log level explicitly from "Warn", "Info", "Debug" or
"Trace" in the configuration.

Default is "Info", fallback for invalid settings is "Debug".

Fixes #34

Note that they are not included in the example configuration files as
these settings can easily mess up everything and should only be adjusted
with great care.

The default settings are valid on Windows 7 and Server 2012 and were
successfully tested on those versions.

Fixes #11

If a new directory is found in incoming but the move operation to
processing failed for some reason, the timestamp and username
directories (and potentially some partially moved data?) would remain
in processing. To prevent confusion about those "incomplete" transfer
candidates they are moved to the "ERROR" location.

Refers to #18

Refers to #18, #29

Refers to #18, #28, #29

Refers to #29

Refers to #28

Refers to #28

Refers to #28

Those objects are not meant to be instantiated directly but only using
the Deserialize() methods which takes care of creating a new object in
case deserializing fails for the status class.