There is an unsaved comment in progress. You will lose your changes if you continue. Are you sure you want to reopen the work item?
Windows Environmental Variables
Add the ability to pass Windows Environmental Variables in the transformation file. Maybe through a switch.
Our use case.
Due to separation of duties, Our shop does not store the environment's unique values in TFS but in an automation program. These unique values are passed to the servers at the time of deployment as Windows Environmental Variables. We currently have %varName%
in the transformation file. Ctt transforms and literally puts %varName% in the xml file.
As a workaround, we run a separate PowerShell task to parse the transformed xml file and replace the %varName% entries with the Windows Environmental Variable's value. I would like to We occasionally run into issues with file encoding due to PowerShell not
natively being able to save the file in the original encoding.
To reduce deployment complexity and risk, we really would like to eliminate the PowerShell step.