Web Deploy Snap-In Bug Report
First of all, the Web Deploy 3.0 PowerShell SnapIn is really good. it takes away the complexity of the msdeploy.exe tool and can be implemented in a PowerShell Tool very well. But i came across two Bugs which have to be fixed to make this tool really GREAT. First and most of all, the Sync-WDSite cmdlet accepts Publishsettings, either as -sourcesettings or -destinationsettings. But if the Publishsettingsfile is not on the Desktop, and doesn't have this name: Microsoft.Web.Deployment.PowerShell.PublishSettings, the cmdlet throws an error. so i had to workaround this issue by simply copying and renaming the correct publishsettingsfile to the desktop and delete it after the sync. not very beautiful. The other bug is that the cmdlet sometimes throws strange errors because of the "Web Application Path Parameter". it said to me for one site that this parameter is already defined, but I didn't define it anywhere. Take my article from stack overflow for reference: http://stackoverflow.com/questions/38991555/sync-wdsite-web-application-physical-path-parameter?noredirect=1#comment65535321_38991555 . when I tried to sync the same site via msdeploy.exe it worked without problems. Please fix these Problems and you tool will be perfect. I'm looking forward to creating a small GUI-Shell Script with this SnapIn/Module! Bye, Simon
Robin coss commented
Ive got same issue and I really don't want to go back to cmdline exe
please fix it as soon as possible it driving me nuts
Sync-WDSite : The parameter 'Web Application Physical Path Parameter' has already been defined
Only seems to affect some of my site?