Hi Rico and welcome to our forums,
There is option for this. If you have an EXE as output (maybe only for testing, in a separate build, if you usually deploy and MSI) you can go to Builds page (old name "Media")
and enable the option
Uninstall a package with the same version. Remember, the option is visible only if you have EXE package set as output for your build.
The EXE bootstrapper is required because of the way Windows Installer works. Basically the situation you encounter should never happen to your users, because every time
you give them an update you increase the version number. But MSFT has never thought about a method to make testing easier of the same package, this is where our solution
is here to help you.
Also, it should be noted that testing repeatedly the same package on the same might give you unexpected installation/application runtime behaviors. Usually virtual machines
are recommended for testing the packages, this way you can restore the machines to the same stage after each test, so previous tests do not affect in any way the outcome
of the latest one, and also this way you avoid the main problem we're discussing here
Regards,
Bogdan
FOLLOW US
Get the latest news in Application Packaging