I’ve noticed that when using the custom install directory, the list of file/folder patterns to exclude from the purge is case sensitive.
I am deploying a .Net application to windows server 2012R2
I have this as a filename to exclude
On my deployment target that config file had the same name, but a different casing.
It was purged.
It would be helpful if this was documented in the custom install step somewhere.
A chekcbox or similar so I could opt-out of case sensitivity.
Since the Windows O/S is not a case sensitive filesystem, maybe there’s something that could be handled depending on the deployment target?