Tools to make it easy to work with parameters in Web Deploy (MSDeploy).
See the changelog for changes and roadmap.
Select the web.config in solution explorer and right-click.
Then select Generate Parameters.xml to have a Parameters.xml file automatically generated from settings in the web.config file. If a Parameters.xml file already exists in the project, missing parameters will be merged into the existing Parameters.xml file.
To control which settings are automatically generated, adjust the settings in the Visual Studio Tools > Options dialog.
Starting in version 2.0, the options dialog also allows the user to select how the default values are generated in the Parametrs.xml file. The default style is clone, which will read the value from the web.config file and copy it into the default value attribute. The other option is tokenize. Tokenize will generate the default value in the format of PROPERTYNAME.
Select the Parameters.xml file in solution explorer and right-click.
Then select Generate SetParameters.xml.
A dialog will then give you the option to add an environment name to the new SetParameters.xml file to be generated.
Either enter an envionment name or leave it blank and then click Create. Then the new SetPameters.xml file is created.
If parameters have been added to the Parameters.xml file, the new parameters can be automatically added to a SetParameters.xml file. Just select the SetParameters.xml file in solution explorer and right-click.
Then select Import Missing Parameters to have any missing parameters automatically added to the selected file.
SetParameters*.xml files will automatically be nested under the Parameters.xml file.
To nest a SetParameters*.xml file that was created prior to installing this extension. Select the SetParameters*.xml file in solution explorer and right-click.
Then select Nest Under Parameters.xml to have the selected file nested under Parameters.xml.
When generating or nesting SetParameters*.xml files, the build action on those files will be set to Parameterization.
This setting will result in these files being copied to the package location and excluded from the package itself.
For cloning and building this project yourself, make sure to install the Extensibility Tools extension for Visual Studio which enables some features used by this project.