Calling migration.exe is always returning exit code -1

[rhuettl]

We're calling the tool automatically and in case of a failure (e.g. exit code -1) we like to start another process. Unfortunately the execution is always returning -1. Any ideas how we could catch a runtime failure? Thanks

[gardient]

I'm calling it by hand but it annoys me as well, managed to track it down to here in the source

Considering ApplicationStopped is called on "graceful shutdown", this will overwrite every exit code to -1

@MrHinsh any insight? I couldn't really tell from the commit and PR.

[MrHinsh]

@ALTrijssenaar has just added a PR #1439 that changes the default behaviour to support this.