New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow XDT Configuration Transforms #331
Comments
ferventcoder
added a commit
to ferventcoder/choco
that referenced
this issue
Jun 16, 2015
ferventcoder
added a commit
to ferventcoder/choco
that referenced
this issue
Jun 16, 2015
ferventcoder
added a commit
to ferventcoder/choco
that referenced
this issue
Jun 16, 2015
ferventcoder
added a commit
to ferventcoder/choco
that referenced
this issue
Jun 16, 2015
If an install.xdt is found, assume that the user meant to change the config with that and replace the overwritten config with the backup. |
ferventcoder
changed the title
Allow Configuration Transforms
Allow XDT Configuration Transforms
Jun 16, 2015
ferventcoder
added a commit
to ferventcoder/choco
that referenced
this issue
Jun 16, 2015
For Xml configuration files that are common with .NET, use Xml Document Transformation (XDT) to change the file over time if the package maintainer includes xdt files. These files are specified in a similar manner to https://docs.nuget.org/Create/Configuration-File-and-Source-Code-Transformations except we only support `*.install.xdt` files and they can be anywhere in the package. They will apply to any configuration file with the same name.
ferventcoder
added a commit
to ferventcoder/choco
that referenced
this issue
Jun 16, 2015
If we are transforming a config file, this means the package maintainer wants the transform to be used to apply changes, so we will replace the backup first and then make changes using the Xml Transform Document (XDT).
ferventcoder
added a commit
to ferventcoder/choco
that referenced
this issue
Jun 16, 2015
Add the following scenarios: - Install a package with a config transform - Upgrade a package with a config transform - Upgrade a package with a config transform when the original config has changes
This was referenced Jun 16, 2015
ferventcoder
added a commit
that referenced
this issue
Jun 16, 2015
…orms (GH-331) XDT configuration file transforms
ferventcoder
added a commit
that referenced
this issue
Jun 16, 2015
* stable: (GH-331) Transformation Specs (GH-331) replace config w/backup if XDT (GH-331) Use XDT transforms on configs (maint) comment grammar (spec) add ExpectedExceptionAttribute override (GH-331) update config/transform for v1.1.0 (GH-331) add transform and config to upgrade pkg (GH-205) Enhance nuspec template instructions Conflicts: src/chocolatey/chocolatey.csproj
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For Xml configuration files that are common with .NET, use Xml Document
Transformation (XDT) to change the file over time if the package maintainer
includes xdt files. These files are specified in a similar manner to
https://docs.nuget.org/Create/Configuration-File-and-Source-Code-Transformations
except we only support
*.install.xdt
files and they can be anywhere in thepackage. They will apply to any configuration file with the same name.
If there is an xdt file, it means the author has chosen that path for making changes to
the configuration file so we will ensure the file that was there before the upgrade is the
file that will get the transformations.
The text was updated successfully, but these errors were encountered: