{"id":2944,"date":"2010-06-25T11:13:24","date_gmt":"2010-06-25T11:13:24","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/webdev\/2010\/06\/25\/a-practical-example-of-using-web-application-deployment-package-with-iis7\/"},"modified":"2010-06-25T11:13:24","modified_gmt":"2010-06-25T11:13:24","slug":"a-practical-example-of-using-web-application-deployment-package-with-iis7","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/a-practical-example-of-using-web-application-deployment-package-with-iis7\/","title":{"rendered":"A practical example of using web application deployment package with IIS7"},"content":{"rendered":"

When a zip package is built from VS2010 web application UI (via Build Deployment Package command), or through command line (msbuild myproject.csproj \/t:package), a few files are generated in the destination folder. Here’s some brief description:<\/p>\n\n\n\n\n\n\n\n\n
File Name<\/strong><\/td>\nDescription<\/strong><\/td>\n<\/tr>\n
myApp.deploy-readme.txt<\/td>\nRead me file of how to use myApp.deploy.cmd.<\/td>\n<\/tr>\n
myApp.deploy.cmd<\/td>\nThe auto generated command file which can be used in many situations.  Check MSDN topic<\/a> for details.<\/td>\n<\/tr>\n
myApp.SetParameters.xml<\/td>\nThe parameter file that user can modify to affect deployed IIS application, such as IIS application name, connection string etc.  Check MSDN topic<\/a> for more details.<\/td>\n<\/tr>\n
myApp.SourceManifest.xml<\/td>\nThe source manifest file that VS uses to compile the package via web deploy.  Not useful after the package is generated.  But user can have a quick peek on what web deploy provider is used when generating package.<\/td>\n<\/tr>\n
myApp.zip<\/td>\nThe package zipped file<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

It’s very common to deploy our package to a IIS7 virtual application under Default Web Site.  Since web deploy can generate a virtual application if it’s not exist, we can use the following options:<\/p>\n

1. Manually import the zip file from IIS manager and change the “Application Path” in the “Import Application Package” Wizard.  (Import a Package through IIS Manager<\/a> )<\/p>\n

2. Change myApp.SetParameters.xml node value of parameter “IIS Web Application Name”:<\/p>\n

\n

<setParameter name=”IIS Web Application Name” value=”Default Web Site\/test1″ \/> <\/p>\n<\/blockquote>\n

\n

Then run “AppServer.cmd \/y” from command line<\/p>\n<\/blockquote>\n

3. In command line or batch file<\/p>\n

\n

Set _ArgMsDeployAdditionalFlags=-setParam:”IIS Web Application Name”=”Default Web Site\/test1″<\/p>\n

AppServer.cmd \/y<\/p>\n

Set _ArgMsDeployAdditionalFlags=<\/p>\n<\/blockquote>\n

4. One line command to deploy the package create virtual application under default web site:<\/p>\n

\n

“D:Program FilesIISMicrosoft Web Deploymsdeploy.exe” -verb:sync -source:package=WebApplication4.zip -dest:auto -setParam:”IIS Web Application Name”=”Default Web Site\/test2″<\/p>\n<\/blockquote>\n

 <\/p>\n

Similarly, if we want to create a new website in IIS7 binding to a new port on a machine, name it AppServer, and deploy our package to it, we can use the following options:<\/p>\n

1. Create the new website manually in IIS manager and import package from IIS manager.  All we need is the zip file on the machine.<\/p>\n

2. In command line or batch file:<\/p>\n

\n

md D:inetpubwwwrootAppServer <\/p>\n

D:WindowsSystem32inetsrvappcmd add site \/name:AppServer \/id:22 \/bindings:http\/*:8090: \/physicalPath:D:inetpubwwwrootAppServer<\/p>\n

Set _ArgMsDeployAdditionalFlags=-setParam:”IIS Web Application Name”=”AppServer”<\/p>\n

AppServer.cmd \/y<\/p>\n

Set _ArgMsDeployAdditionalFlags=<\/p>\n<\/blockquote>\n

\n

Or make it a little bit fancy:<\/p>\n

Set _ArgMsDeployAdditionalFlags=-presync:runCommand=”md D:inetpubwwwrootAppServer & D:WindowsSystem32inetsrvappcmd add site \/name:AppServer \/id:22 \/bindings:http\/*:8090: \/physicalPath:D:inetpubwwwrootAppServer” -setParam:”IIS Web Application Name”=”AppServer”<\/p>\n<\/blockquote>\n

\n

AppServer.cmd \/y<\/p>\n<\/blockquote>\n

\n

Set _ArgMsDeployAdditionalFlags=<\/p>\n<\/blockquote>\n

3. One line command to create a new web site in IIS and deploy package to it.  All we need is the zip file on the machine.<\/p>\n

\n

“D:Program FilesIISMicrosoft Web Deploymsdeploy.exe” -verb:sync -presync:runCommand=”md D:inetpubwwwrootAppServer & D:WindowsSystem32inetsrvappcmd add site \/name:AppServer \/id:22 \/bindings:http\/*:8090: \/physicalPath:D:inetpubwwwrootAppServer ” -source:package=WebApplication2.zip -dest:auto -setParam:”IIS Web Application Name”=”AppServer”<\/p>\n<\/blockquote>\n

Hope this simple sample can generate more interest to use web deploy as packaging and deploying method.<\/p>\n

 <\/p>\n

Xinyang Qiu<\/p>\n

Web Platform And Tools<\/p><\/p>\n","protected":false},"excerpt":{"rendered":"

When a zip package is built from VS2010 web application UI (via Build Deployment Package command), or through command line (msbuild myproject.csproj \/t:package), a few files are generated in the destination folder. Here’s some brief description: File Name Description myApp.deploy-readme.txt Read me file of how to use myApp.deploy.cmd. myApp.deploy.cmd The auto generated command file which […]<\/p>\n","protected":false},"author":404,"featured_media":58792,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197],"tags":[7336,7352,7323,7329],"class_list":["post-2944","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aspnet","tag-msdeploy","tag-package","tag-visual-studio-2010","tag-web-deployment"],"acf":[],"blog_post_summary":"

When a zip package is built from VS2010 web application UI (via Build Deployment Package command), or through command line (msbuild myproject.csproj \/t:package), a few files are generated in the destination folder. Here’s some brief description: File Name Description myApp.deploy-readme.txt Read me file of how to use myApp.deploy.cmd. myApp.deploy.cmd The auto generated command file which […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/2944","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/users\/404"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/comments?post=2944"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/2944\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media\/58792"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media?parent=2944"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/categories?post=2944"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/tags?post=2944"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}