This commit is successfully tested to work on Windows 7 with the latest
version of RoboSharp (at the time of writing, including the
[EnableRaisingEvents fix][1] which has not yet been merged upstream).

This closes #15

[1]: https://github.com/tjscience/RoboSharp/pull/46

Refers to #3, #11, #15

The shared approach results in conflicts if the generated class is used
in ATxCommon which is imported in the other projects. This way we can
use the symbols defined via ATxCommon in all depending projects.

The downside is that it slows down the build-process a bit as every
build from a project depending on ATxCommon (read: all others) will
change the generated code and thus force a re-build of ATxCommon and
the project itself. Since building the entire solution is still just
a matter of seconds, that's a fair trade-off.

See https://stackoverflow.com/a/10334095/2018314 for details on sharing
resources among multiple projects in a solution.

There is no need to have this only as a post-build event, providing it
at this stage will allow us to include it in the assembly information.

Refers to #18

Refers to #18

Refers to #18

Add the template files as links to the ATxService project, pointing to
the central "Solution Items" files and mark them for copying to the
build output location. Update the Make-Package script accordingly.

Restoring the "heartbeat" functionality without the overhead of
serializing the XML every second.

By removing the AdminDebugLog() method we're basically done with
switching to NLog for logging and therefore this closes #3.

Closes #9

Currently there are no references to the object before a transfer has
started, so it is safe to only initialize it in the StartTransfer()
method.

Refers to #2, #26

Refers to #26

Refers to #3, #4

Refers to #4

Having the total progress is much more useful than for the individual
files, especially for transfers with many files.

Closes #26

Refers to #26

Refers to #24

Refers to #3

Refers to #3