I don't want to install Slow Cheetah on all the build servers.
We are using Slow Cheetah for config transformations and it is working perfectly fine. It generates multiple app.config files and we make changes to them as desired.
We have setup several servers. All of them has their code repositories, they pull the code from command line and build the packages accordingly. Those codes has those config files in it. But still when we compile the application from command line, packages are not generated with the transformation if slow cheetah is not installed on them. Otherwise it works fine.
We never know when we setup a new server and a new user, so it is not possible to install Slow cheetah on every one of them
It is possible somehow to use slow cheetah dll in the application and call the transform method manually from it?
Thanks
This article is a reference. Step 1: Install the package "Slow Cheetah" into your solution. Step 2: Right click on the App.config and select the option Add Transform. Step 3: To tweak the appsetting values ,connection strings etc based on the configuration environement. Here I am tweaking the webServiceUrl value based on environment.
All the functionality is installed to %LOCALAPPDATA%\Microsoft\MSBuild\SlowCheetah\v1\ and lives in a standard MSBuild .targets file. You don't even need the plugin if you are installing this on a build server, just copy the files or even check them in with your source and refer to them in your project or MSBuild files.
This is good for team scenarios, other team members don't need to have SlowCheetah installed for the transforms to kick in Bunch of bug fixes, for the full list see closed issues in 2.5
SlowCheetah supports transformations for XML files, specified by XDT and for JSON files, specified by JDT. Transform files created by the extension follow these formats. Perform transformations of XML and JSON files on build per configuration and publish profiles. Quickly add and preview transformations to a file in the project.
The most recent version of SlowCheetah (2.5.14) is available on Nuget. When adding via nuget it is stored in the packages
folder in the local solution directory (like all nuget packages) which means it should work on any build server out of the box now.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With