Skip to content

Instantly share code, notes, and snippets.

@sayedihashimi

sayedihashimi/comments.md

Created February 25, 2016 16:31
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save sayedihashimi/3ccab545c0d682d9808b to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save sayedihashimi/3ccab545c0d682d9808b to your computer and use it in GitHub Desktop.
Download ZIP
Raw
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

@rschiefer
Copy link
Copy Markdown

rschiefer commented Feb 25, 2016

Thanks for reviewing the post and providing this feedback! A few questions/comments:

RE: Targets - Thats why I added the "marketing term" qualifier. I think most people lump the Package target and VS publish together as WebDeploy. I will add "Technically, the targets are not part of WebDeploy but they are closely related." Sound okay?

RE: MSBuild version - I intentionally did this so the commands would work all the way back to VS2010.

RE: deploy.cmd bugs - I have seen some of these errors but we are currently using the deploy.cmd successfully for many deployments (40-80). That being said we are always open to improving our capabilities and avoiding issues.

RE: archive.xml - that helps thanks! I will clarify.

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

RE: sitemanifest extension - this is a great link that I will add.

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

@sayedihashimi
Copy link
Copy Markdown
Author

sayedihashimi commented Feb 26, 2016

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment