MS Installer

  • Thread starter Thread starter Lee Mellinger
  • Start date Start date
L

Lee Mellinger

We use MS Installer to install a Windows our windows application. We
want to be able to install a new version and have the prior version
removed automatically. When we set the Version, we answer Yes to reset
the ProductCode and PackageCode. RemovePreviousVersion=True. However,
during installation, the prior version is not removed and a new entry in
Add/Remove Programs is added. This is the proper procedure according
the documentation. Am I missing something?

Thanks!
 
Are you incrementing the Version or trying to trick it? I was trying to
outsmart the installer by changing the Version, generating new GUIDs and
changing the Version back. That doesn't work.

Also be sure to leave the UpgradeCode the same.

-Eric
 
I have the same problem. Here is a description of my build process.

Assume
------
Current beta release build version is 1.5.0.11
Current product code: {622EC8CC-030F-494E-8C9F-127577B1C4FE}

To make a new Build 1.5.0.12
----------------------------
1 - Increment the product version number, for example, 1.5.0.11 to 1.5.0.12.

2 - I select the previous beta build MSI file to upgrade, in this
example the 1.5.0.11 build. When I do this I get a warning that the
previous version matches the current product code. I click yes, to make
it update the current product code.

3 - The new current product code is: {9C4D9485-94DF-4B60-A1B0-44A21130C392}


After installing three or four builds, I have the same number of
installs in my Add/Remove program list.

It seems strange that whenever I select the previous MSI build for
upgrading, the upgrade code GUID remains the same.

Any tips or suggestions are much appreciated.

( This MSI install stuff has a steeper learning curve than I expected. )

-Ed
 
My problem is solved.

MSI only checks the first three number of the product version number for
upgrades.

I changed my version number format from:
1.5.0.11

to:
1.5.11

If that would not have worked, I was told to "try placing the
RemoveExixtingProducts between the InstallValidate and the
Installinitialize action. For more about RemoveExictingProducts action
check the msi.chm."

-Ed
 
Yes, Visual Studio .NET won't even let me enter a build number in Version
field. I get this error:
C:\Projects\dotNET\\PMUI\Production\Patch\Patch.vdproj Invalid product
version '3.0.2.1'. Must be of format '##.##.####'

I'm surprised that this is not allowed as I thought this is typically used
to indicated the number of the builds done within a given day.

-Eric
 
Yes, Visual Studio .NET won't even let me enter a build number in Version
field. I get this error:
C:\Projects\dotNET\\PMUI\Production\Patch\Patch.vdproj Invalid product
version '3.0.2.1'. Must be of format '##.##.####'
Click to expand...

Wise for Windows Installer does not stop you from entering in a 1.2.3.4
number format. I wish it had stopped me like Visual Studio .NET does or
at least warned me.

I'm surprised that this is not allowed as I thought this is typically used
to indicated the number of the builds done within a given day.
Click to expand...

That's what I was using it for. I am doing "1.5" beta test program. I
increment the build number on average about once a day and post a new
beta. Once there are no more show-stopper problems, then build 1.5.34
becomes the shipping release.

-Ed
 
Back
Top