The VSIX package model differs for VS2017, this package will need rebuilding.

I think the best option might be to start a new version of the package.

I don't intend to make this change until we get an RTM of VS2017

The tool should any entries for non default values in the connectionstrings node.

generate parameters.xml content

command line execute
msdeploy -verb:sync -source:contentPath=.... -dest:package=xxx.zip -declareParamFile="parameters.xml"

response
Error: 需要元素 'parameterEntry'。
parameters.xml
Error count: 1.

if change parameters.xml content

execute correct

Not an issue but a simple feature request. In VS under Tools/Options menu and then 'Parameters XML Addin', could you please add an option to change the pre and post tag/token characters? You currently default to double underscore. It would be immensely handy to change these since I use the popular "Replace Tokens" TFS task from Guillaume Rochon (found in TFS marketplace) - which defaults to "#{" and "}#".

Thanks for your consideration!
Chris

When I try to install the plugin the installation does not correctly install.

The log result:

04/12/2015 11:05:10 - Searching for applicable products...
04/12/2015 11:05:11 - Found installed product - Microsoft Visual Studio Premium 2013
04/12/2015 11:05:11 - Found installed product - Microsoft Visual Studio Professional 2013
04/12/2015 11:05:11 - Found installed product - Microsoft Visual Studio 2013 Shell (Integrated)
04/12/2015 11:05:11 - Found installed product - Global Location
04/12/2015 11:05:11 - Found installed product - ssms
04/12/2015 11:05:11 - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.
at VSIXInstaller.App.InitializeInstall()
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.Execute()

The parameters.xml file this is added is set to a build action of 'content'. It should really be 'none' so it is not copied to the deployed web site

Hello,

The extension generates a warning when installed on VS 2019.
It seems to be using a synchronous load, which is now deprecated.

Cheers !

Thank you for this add-on. I noticed that AppSettings where included in the generated Parameter.xml file but not the connectionStrings like so:

I wanted to understand how to generate a nested parameters in parameters.xml - for that, tried to use this plugin. But this plugin did not generate anything for this parameter in web.config:

<mycompany>
  <clientweb enableuserregistration="true" enablecustomerautoredirect="false">
    <defaultSSOFailedLogin title="Login error" description="Unable to log in" />
  </clientweb>
</mycompany>

Allow the parameters.xml to be generated from an App.Config to let this basic MSDEPLOY pattern of managing versions be used for .EXE and .DLL config files

The generator now always adds a not so useful description attribute: description="Description for cdnUri".

I would like to have the option to generate a Parameters.xml file without the description attributes

Thanks for your great extension!

Here's a small change that would make it even better for me: make the casing for the "defaultvalue" attribute value configurable.

Now it's always an uppercase version of the "name" attribute value: defaultvalue="CDNURI".
An alternative casing option I would like to have is leaving the case unchanged: defaultvalue="CdnUri"

When editing a website project instead of a web application project, no context menu appears for the web.config file.

It is possible for endpoint to appear in the <system.servicemodel> block

These should be generated into the parameters.xml file too