As discussed here,
I am trying to deploy a project contains PS and config files.
When using the “Substitute Variables in Templates” argument, the PS file content is encoded;
How can I avoid this encoding or use an ASCII (7-bit) encoding for that file?
This is something that has come up a few times, we’ve actually added an additional field to the “Substitute Variables in Templates” feature that allows the desired encoding to be specified:
e.g.
If you don’t currently see that as an option, then an update to the latest version should add this for you.
If upgrading isn’t possible currently, the only other option I can think of would be to add a post-deployment script that re-encodes the files as needed.