| We made the experience that MKS Source changes content of binary files, probably since we have upgraded to MKS2009 version. The change of the regarded binary files seems to be triggered by the archive type of these files, which is set automatically to text by the MKS source system. The workaround provided by MKS to prevent change of (binary) files after standard check in and check out actions consists of inclusion of the type of file characterized by the file extension into a policy. This is absolutely not practicable for us, as we cannot check any file by extension whether it is changed by the MKS system or not and include it in a policy. Furthermore the described behaviour is absolutely not what we expect from a version control system. We expect from a version control system that whatever file is put under version control, this file is NEVER changed automatically or non-transparently by the system. Does anyone know a method how we can prevent generally the automated change of whatever files by the MKS Source system ?|
Please be aware that the same can happen or happens on your MKS source system without that you notice it.
|Posted By: mlizak Posts: 72 / Registered: Feb, 2011|
| Hello Andreas,|
Please contact Integrity Support so that we can assist you with this issue.
For the danger of being off-topic:
Hopefully this entry is helpful in your context.