Bug: Remote Execution Task errors while retrieving remote log file

[Gaikotsu2]

If the RemoteDropkickExecutionTask is unable to copy the remote log file back to the local folder it throws an error causing the deployment to stop.

This is easiest to replicate if the person running the deployment does not have write permission to the folder the deployment is run from as is usually the case when using a continuous build system.

Recommendation: instead of copying the file back to the local folder, just read the file from the remote location

[ferventcoder]

You do realize that the other logs don't work either (but they don't cause the deployment to stop either).

Wouldn't it be a better idea to always log to a folder you know you can log to?

The idea here is a unifying folder under ProgramData\ChuckNorris where RH, DK, UC, etc put logs and application type data.