It is not recommended that the update add or remove files, registry entries, or shortcuts from a shared component.Ī small update is shipped as a Windows Installer package. 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. 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. 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. If the update modifies a versioned file, that file's version must be incremented in the File table. The update can add, remove, or modify the files, registry keys, or shortcuts of components that are not shared by two or more features. msi file without changing the file's name. Note that this means that the update can change the tables, custom actions, and dialog boxes in the. Instead, because it modifies the package, it should change the package code. The update must not change the name of the. Consequently, a small update or minor upgrade must never change the name of a component's key file because this would require changing the component code. The update must not change the component code of any component. The update can add a new component or a new or existing feature. If it removes a parent feature, it must also remove all the child features of the removed feature. It can add a new feature to the existing feature-component tree. The update can enlarge or reduce the feature-component tree, but it must not reorganize the existing hierarchy of features and components described by the Feature and FeatureComponents tables. In the Access Solution Wizard, the product code field is a GUID that is the principal identification of an application or product.
0 Comments
Leave a Reply. |