laazyj/dropkick — Issue #4: Errors are not always reported on Dropkick console/logs when deploy fails
Author: laazyj
Created: 2012-02-08 09:05:40+00:00
State: open

The repeatable example is an IisDeployment with Https binding that uses a CertificateThumbprint that doesn't exist on the target server.
Running Dropkick in verify mode reports the error correctly, but running Execute doesn't, it just skips a few steps and continues.

Is it perhaps to do with the try..finally used to stop/start the app pool in the project's deployment plan?