Hi,
Could you be more specific about what these improvements are?
These synchronization improvements affect the behavior shown when the target directory (on the disk) of a synchronized folder is missing. Also, when setting a folder as synchronized, the default synchronization path is now the original path of the folder on the disk. Another synchronization improvement affects the Advanced Installer
command line interface by adding the "-clearcontent" parameter to the
/ResetSync command.
This is a bit of a bugbear for those of us who need to use the patching functionality in the 'real world', but having to add new files manually into the project is quite painful.
Please note that the synchronization mechanism has some contradictions with the patch concept. Perhaps in the future we will find a way to use them together safely, but unfortunately this will not be soon.
will it preserve the Component ID and attributes, if a refresh on the folder is performed for objects that have not changed name or location?
Yes. The components are re-created only if:
- files from the synchronized folder are removed and then re-added
- files are moved from their original location
- files are renamed
Also will project file attributes be preserved across a sync for existing files.
The attributes of a synchronized file are maintained as long as:
- the file is not moved from its original location on the disk
- the file is not renamed
- the file is not removed and then re-added in the synchronized folder on the disk
Regards,
Cosmin
FOLLOW US
Get the latest news in Application Packaging