Currently if MSDeploy v2 is not installed the publish is not performed but a "silent" error occurs.
Better would be to give an error, we should also create a mechanism (env variable?) that users can specify the full path to msdeploy.exe which should be used.
Details
Here is the implementation in Publish-Interactive.ps1 which needs to get updated
function GetPathToMSDeploy {
return ("{0}\IIS\Microsoft Web Deploy V2\msdeploy.exe" -f (Get-ChildItem env:"ProgramFiles").Value)
}
Currently if MSDeploy v2 is not installed the publish is not performed but a "silent" error occurs. Better would be to give an error, we should also create a mechanism (env variable?) that users can specify the full path to msdeploy.exe which should be used.
Details
Here is the implementation in Publish-Interactive.ps1 which needs to get updated