The package must be detected as present; the feature the package is associated with must be removing (during a full removal, or the feature is unselected in maintenance); the package must have a remove operation.
With this information I've found, that the path to the target is the problem. While at the installation operation, there can be started without path, the other operations seam to need a path in the target.
Will there be a posiblity to get the productcode of the used/installed MSI, as used in the condition? My aim: [SystemFolder]msiexec.exe /x {*} I don't want to use a hard coded productcode, as long as the next built will create a new one.
You'll either need to reference a path (such as [ISPREREQDIR] or [SETUPSUPPORTDIR]), or the GUID. If you're trying to install and remove a .msi file, I would strongly recommend using the .msi package type instead of the .exe package type, as it will handle all of this for you. Otherwise you could try some sort of automation to tweak the project to use the correct product code before you build it.
