|
WARNING Deleting a feature is quite a rigorous measure with a high potential for extensive side effects. Make sure to double-check the relation and content status of a feature before actually deleting the logical feature object! |
To trigger the feature deletion, packagers should select the feature in the tree view structure within the Features view. Once a feature is selected, its deletion is initiated either by hitting the delete key or by right-clicking the feature and picking Remove from the context menu.
Either way, packagers are by default requested to confirm the intention of the deletion. Even though the confirm dialog may be suppressed by activating the "In future do now show this confirmation for delete operations" checkbox, it is recommended to keep it for security reasons. Deleting a feature deletes the overall settings and logical relations between the contents managed by that feature. The contents themselves, such as files, registry keys, and the like, are preserved. In a worst case scenario the components of a deleted feature become orphaned. Those unmanaged components will never be installed. Windows Installer databases with orphaned components are not standard compliant, and will fail any attempt to install the target package.
Nonetheless, if a feature must be deleted, the confirm dialog offers a button REMOVE to do exactly that. Clicking that button deletes the feature and all child features, while preserving all components stored within the feature or its former children.
|
Note: As soon as the feature object is deleted from the Feature view, its resembling data row marked as deleted within the affected Installer database table. Once the packaging project is saved or the history of changes is cleared, the feature object is no longer visible at all. |
