Changing product version # can force upgrades to fail

[sdeschenes]

If I change the product version # in the installer, performing an upgrade on a previously released version of the same installer prompts a message saying "The feature you are trying to use is on a network resource that is unavailable." The message then proceeds to instruct me to click OK to try again or enter an alternative path to the folder containing the installation package. When I select Cancel on this message, the installer continues to execute commands and then fails.

Why would changing the version # have this kind of effect on an upgrade?

I have encountered this issue in the past and the only way to resolve it is to create a brand new installer project. I have multiple install projects, so I shouldn't have to create new installer projects if I want to change the product version #.

[MichaelNesmith]

From what you describe, it sounds like just changing the product GUID would help. But that said, I am not sure why you're running into this issue - some bare-bones projects to reproduce the actual problem would help.

[sdeschenes]

I have uploaded two bare-bones installers for reproducing this issue and have uploaded the project used for building the installers.

*Note: I used the multi-instance project, but I made a slight alteration. The upgrade installation will "overwrite" the original installation. You will not see an additional entry in Add/Remove programs. This is because I want to maintain the illusion of one installation. This alteration may or may not be an intermediate cause of the problem I am experiencing, but felt it was worth mentioning.

[MichaelNesmith]

That alteration is your culprit, I'm afraid!

[sdeschenes]

I was hoping you wouldn't say that.

[sdeschenes]

Do you know why this happens?