IT:AD:WebDeploy:HowTo:Manually Deploy a Package on a Target IIS
Summary
After having created a WebDeploy Package, it needs to be shipped somehow to the target environment, and installed.
Process
The Target Web Site will have to exist first.
Under the Hood: Regarding Parameters.xml
When using IIS's wizard, it will not use the the {project}.Parameters.xml file that is used when doing it the /.cmd* way.
All the customisable settings will be defined from the UI that IIS provides, which is being developed using the prompts and default values that were hard-cooked into the zip's {project}.SetParameters.xml file when you built it.
As the Parameters are inside the zip, and put there during the phase of building the project, Packages are very delivery target specific. As the parameters within {project}.SetParameters.xml are generated during build from a combination of PubProfile settings and Parameters.xml file, one has to insert those values early.
Manual Deployment
On the Target IIS instance, use IIS's wizard to select the package:
Note that zip package is more than just files – but IT:AD:MSDeploy verbs
Notice the Advanced button…
For the extended features/settings…
- Enter the Application name in the website you are publishing to
- Finished