Keep ComponentID the same between different versions

[davidesharpe]

How can I keep the ComponentID of components the same between different versons of product, so that Patch build doesn't throw up so many warnings ?

I'm assuming this is because of Synchronised folders ? all that i am changing currently is the product version number, and I'm not changing the product id between builds.

[mihai.petcu]

Hello,

The warnings occur because this is against patching rules as described in our user guide article.

The components' GUIDs shouldn't change between versions if you don't resynchronize the folder from the GUI. After you upgrade the folder content on the hard disk, you can refresh the synchronization in the GUI from the Refresh toolbar button. This is the recommended operation in order to maintain the same components' GUIDs when authoring a patch upgrade.

All the best,
Mihai

[davidesharpe]

So If (as in this case) i'm running the AI build from an automatic final builder task, how can I ensure that the build (pulls in any new files that have been added, but keeps the guids of existing ones the same ?, is there a command line option to 'resynch, keeping guids)

Thanks

[mihai.petcu]

Hi,

Here is the command option to help you with this.

All the best,
Mihai

[davidesharpe]

So let me confirm this behaviour will work as hope.

assuming this all happens from the command line.

1. i have created a msi normally (say product1.1.1.msi)

The dev guys make some changes that will change a few dlls and possibly add a couple too)

2. I update the product version (keeping product id the same)

3. I do a reset sync folders as you suggest

4. I build an msi (product1.1.2.msi)

The result will be that the GUIDs of the common files between the two builds will remain the same, but the build will pick up the few new dlls that have been added to the product

I will then be able to succesfully build a patch from these two images.

is that how it should work ?

[Bogdan]

Hi,

Yes, this is correct. Reseting the synchronization should make the existent components to keep their GUIDs and therefor allow
you to successfully create the patch.

Please note that enabling back the synchronization will break the patch for a future version.

Regards,
Bogdan