@PCAssistSoftware
I swear that I had added the '-1' enum to this exit status, along an accompanying boolean status check to one of my pull requests/commits. I can't find out/remember which one had it though.
Anyway, the cause for that is because if the process encounters a serious error that simply causes the process to fail (or you cancel the job via RoboCommand.Cance()), you will get an exit code of -1 because robocopy didn't report a result, the process just exited without finishing.
In my program, since I allow users to cancel jobs, I have to check for the exit code value == -1. I believe this should be value within the enum since it is possible to come across.
@PCAssistSoftware
I swear that I had added the '-1' enum to this exit status, along an accompanying boolean status check to one of my pull requests/commits. I can't find out/remember which one had it though.
Anyway, the cause for that is because if the process encounters a serious error that simply causes the process to fail (or you cancel the job via
RoboCommand.Cance()), you will get an exit code of -1 because robocopy didn't report a result, the process just exited without finishing.In my program, since I allow users to cancel jobs, I have to check for the exit code value == -1. I believe this should be value within the enum since it is possible to come across.