MafaldaHello,
I'm using wyBuild to create updates for my applications. I experiencing some problems related with the files updated.
For example: my application is having some exe's folders and config files. My first version have the basic configuration of the config files. After install the firs version I modify locally this configuration. Then I prepare another release but without modify config files, these are the same as the first release. Then sometimes ( not always) the auto update crushed de config files and the local configuration is lost, however in the release version there isn't any modification.
Is it a bug? why is replacing config files if it haven't been modified?
wyBuild changes files when updating from version A to version B in the following cases:
- Config file is in version A, but removed in version B (the files is deleted)- Config file is in version B, but not in a (the file is added)- The file differs between version A and B (the file is patched).
To tell wyBuild to leave your config files alone, just remove the config files from all versions in wyBuild. It will then ignore them whether they changed or not.
MafaldaThanks, for your reply 🙂
I understand your explanation but I have a strange behaviour in some particular case.
I investigate the root cause and seems something related to replace manually one of the files of the application in order to test it.
My question now is what happens if the version A is really A* because some file is modified manuallly and I try to update to version B. But the updates are done from A to B. The result of A* to B I supose that wyBuild can't use correctly the patches and some strange behaviour occurs. Can you tell be, what does the software do if this happens?
If a customer changes a file that will be patched in the next update, then wyUpdate downloads the "catch-all" update.
