Uninstall Win32 app dependencies
Dependency are generally not uninstalled when uninstalling the parent package. This may be OK in some cases but prevents the use of dependencies in many others.
Think of components like
- a configuration package
- a main install package
We might add the main install package as a dependency to the configuration package so that it would be installed before the configuration.
This would allow for a simple changing of the main package version without touching the configuration and multiple configuration packages using the same main package.
But what if I want to uninstall the application?
Uninstall of the main package should uninstall dependencies if the admin needs that.
This may be solved by providing a dependency property that may be configured by the admin.
Some dependencies need to stay, some should be uninstalled on uninstall of the main package if they are not needed by another package or maybe even forced uninstalled irrespective of other packages (which might lead to a reinstallation thereafter).