Comments on http://dotnetcatch.com/2016/02/25/the-anatomy-of-a-webdeploy-package/

comments.md

In summary, WebDeploy (the marketing term) includes MSDeploy binaries, MSBuild extensions (*.targets files), Visual Studio extensions and the Web Deployment Agent Service.

The targets are not really a part of Web Deploy but instead of the Visual Studio Web Projects which are implemented in MSBuild and then invoke MSDeploy

C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild /t:Package

You're using an old copy of msbuild.exe but for your scenarios it's likely OK.

FYI the deploy.cmd file has some bugs and in some scenarios doesn't work well. I'd only use that as a starting point or for basic scenarios

archive.xml is an internal file created when the package is created by msdeploy and shouldn't be hand modified.

Instead of the .cmd file I bet we could get my new powershell script setup for ASP.NET 5 https://github.com/aspnet/vsweb-publish modified to work with ASP.NET 4 projects. I'd love to work with you on that.

For sitemanifest you can add elements into your project/pub profile to add elements see http://sedodream.com/2011/11/08/settingfolderpermissionsonwebpublish.aspx

RE: Targets

Sounds good

RE: MSBuild version

Sounds good

RE: deploy.cmd bugs

OK great, there are some things that it doesn't work for but I forget specially what

RE: your PS script - I would really like to work with you on this! Whats the best way to proceed?

We should meet over skype if possible. Please email me at sayedha@microsoft.com

If its okay, I would like to thank you for reviewing and helping to clarify points at the bottom of the post.

Of course