rboy1 wrote:
I'm sure there is a simple work around though, no ?
First part of the delete function would be to verify whether the file ( or path to the file) exists (dir command on Windows, i suppose) and if it does, issue delete command.
This way you can reach 99% certainty that file WILL be deleted at the end of the function.
If path to the file does NOT exist, skip delete command and log it into the history file to be attempted again.
The key assumption you mentioned below is : If it's unsuccessful again, skip and move on There is way to tell right now if the delete command was successful or not. A limitation of the way Microsoft has Designed .NET You see the issue here?You mean there is NO way to tell if command was successful or not ? If so , no I did not know that. I've not touched Windows machine (besides HTPC) for decade.
I'm sure there is a simple work around though, no ?
First part of the delete function would be to verify whether the file ( or path to the file) exists (dir command on Windows, i suppose) and if it does, issue delete command.
This way you can reach 99% certainty that file WILL be deleted at the end of the function.
If path to the file does NOT exist, skip delete command and log it into the history file to be attempted again.