| Quote |
1). The update can add, remove, or modify the files, registry keys, or shortcuts of components that are not shared by one or more features. If the update modifies a versioned file, that file's version must be incremented in the File table. If the update removes resources, it should also update the RemoveFile and RemoveRegistry tables to remove any unused files, registry keys, or shortcuts that have already been installed. 2). The update of a component that is shared by two or more features must be backward compatible with all applications and features that use the component. The update can modify the resource of a shared component, such as files, registry entries, and shortcuts, as long as the changes are backward compatible. It is not recommended that the update add or remove files, registry entries, or shortcuts from a shared component. |
From this it appears that if a component can be installed by more than 1 feature then the install cannot be properly updated. This sounds bizarre to me, or am I reading it wrong. Does anyone have any idea of what problem this will cause. I have created a few initial patches and so far I can't see any problems created by having a component belong to more than 1 feature. Does anyone have any more information on these two clauses or experience in the problems caused by not obeying these particular rules.
If they do cause major problems, then is there any way aroung these problems.
Thanks,
Andrew
