Skip to content
| Marketplace
Sign in
Azure DevOps>Azure Pipelines>Website Transform
Website Transform

Website Transform

Luuk Sommers

|
345 installs
| (0) | Free
Task to apply XDT transform on XML files. This is a fork from the original from https://github.com/qetza/vsts-xdttransform-task with wildcard support
Get it free

Important notice

This is a fork from https://github.com/qetza/vsts-xdttransform-task all credits go to the original author. Please donate to him for his awesome work. My work is only a poor implementation for wildcard support.

Donate

XDT transform task

Visual Studio Team Services Build and Release extension that applies XDT transforms on XML files.

Usage

Add a new task, select XDT Transform from the Utility category and configure it as needed.

XDT Transform parameters

Parameters include:

  • Working folder: the working directory for relative paths. If not specified the default working directory will be used.
  • Transformations: an absolute or relative comma or newline-separated transformation file rules.

Syntax: {xdt path} => {xml path}[ => {output path}]

  • web.release.config => web.config will apply web.release.config to web.config and update the file.
  • xdt\web.release.config => config\web.config => web.config will apply xdt\web.release.config to config\web.config and save the result in web.config.
  • *.release.config => .config enabled wildcard search, the search should start with *. This will apply all {filename}.release.config files to the {filename}.config of the same name. The search is recursive from the working directory.
  • *.release.config => .config => .xml enabled wildcard search, the search should start with *. This will apply all {filename}.release.config files to the {filename}.config and save it in the {filename}.xml. The search is recursive from the working directory.

Tips

You can use the XDT tranform task to inject tokens in your XML based configuration files configured for local development and then use the Replace Tokens task to replace those tokens with variable values:

  • create an XDT transformation file containing your tokens
  • setup your configuration file with local developement values
  • at deployment time
    • inject your tokens in the configuration file by using your transformation file
    • replace tokens in your updated configuration file

Debug

You can set the variable system.debug to true to enable the debug logging on the task to help you investigate unexpected behavior of the task. If you cannot fix your issue, open an issue on the github repo and i'll help you :)

Release notes

New in 3.0.0

  • Add support wildcards.

New in 2.1.0

  • Add support for comma separator in Transformations parameters.

New in 2.0.0

  • Breaking change: All previous parameters are now merged in a single line using syntax {xdt path} => {xml path}[ => {output path}].
  • Add support for multiple transformations.
  • Add Working folder parameter for root of relative paths.

New in 1.0.0

  • Initial release
  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2025 Microsoft