The issue is that if we bump the version number to be higher it was not upgrading at all for some reason. The build number is the only thing that (not including binaries)changed and we use a 4 digit build number for example 0114.
If I bump our version to 0201 its not considering it an upgrade. If I change it to 5 digits which we were planning on doing it does consider it an upgrade and throws the prompt this will perform an upgrade of the product. If you click yes you are greeted by the resume setup dialog after seeing the extracting msi phase complete. If you progress through the dialogs and finish and examine the binaries none of them have been replaced with newer versions.
I believe this is partially b/c we violated the upgrade rule by removing a component and not making it a major upgrade. I don't mind doing this but I would like to understand what else we are doing wrong. If I rev the product and package guids and bump the version and make an entry for the upgrade table the upgrade works just fine. However, a byproduct of that is the old install will no longer detect the newer version since its a different package and allows both installs on the system at the same time (tries to overwrite the binaries and creates a 2nd entry in add/remove programs).
Where if the product/package guids are the same it says I have detected a newer version of the product blah blah blah.
Since I cannot go back and change the last release what can I do to the current one to preserve the downgrade prevention and allow the upgrade to work properly?
Edited by overlordchin, 23 July 2012 - 19:29.