Setup of a .NET Installation

[Glyn Meek]

We are having great difficulty configuring the 'setup' project in .net and
making it so that it will OVERWRITE and REPLACE previous versions. We have a
number of Visual Basic products in our suite, and have built separate Setups
for each of them. Ths Setups work fine apart from one little glitch which
forces us to do a manual 'Unload' of previous versions.

We have set the 'DetectNewerInstalledVersion' flag to True, AND the 'Remove
Previous Versions' flag to True, but the installation still will not work
unless we go through 'Control Panel-> Add or Remove Programs' first and
'manually' uninstall the previous version.

Can anyone tell me what we are missing here as this is holding up our
release.

Regards and thanks

Glyn J Meek

 

[Josip Medved]

We are having great difficulty configuring the 'setup' project in .net and

making it so that it will OVERWRITE and REPLACE previous versions. We have
a number of Visual Basic products in our suite, and have built separate
Setups for each of them. Ths Setups work fine apart from one little
glitch which forces us to do a manual 'Unload' of previous versions.

We have set the 'DetectNewerInstalledVersion' flag to True, AND the
'Remove Previous Versions' flag to True, but the installation still will
not work unless we go through 'Control Panel-> Add or Remove Programs'
first and 'manually' uninstall the previous version.

Can anyone tell me what we are missing here as this is holding up our
release.

change version property of setup project...

 

[Gene Vangampelaere]

Change it to a version higher than 1.0.0
I noticed that using 0.0.1 ... did not work properly.

 

[Phil Wilson]

You're right, VS setup projects start the version at 1.0 and don't upgrade
versions below this with a RemoveExistingProducts. The other thing to watch
out for is that an Everyone install won't upgrade a Just me and vice versa.
Also the ProductCodes must be different but the Upgradecode needs to be the
same.