From MSI to WiX, Part 8 - Major Upgrade

re: From MSI to WiX, Part 8 - Major Upgrade

Anudeep Debnath — Mon, 07 Jan 2013 11:45:32 GMT

Hi Alex,

I am facing now a days problem with upgrade. I made a Web Application upgrade with proper rules of upgrade but it is not copying files from source directory. It will make double entry in 'Program and features'. and not upgrade the previous version. I made everything proper as I seen. I checked UpgradeVersion, AdminUISequence, InstallUISequence, InstallExecuteSequence. Everything in a right manner. It is not working. Whats the problem? Whats I am missing?

re: From MSI to WiX, Part 8 - Major Upgrade

SCCM — Mon, 17 Jan 2011 18:48:24 GMT

I've have built same code with two different version numbers. Installed the first MSI and tried to use the second to uninstall (I was hoping that would work as the upgrade code is the same); however, I get "Another version of this product is already installed" message.

Plz help......

re: From MSI to WiX, Part 8 - Major Upgrade

SCCM — Mon, 17 Jan 2011 18:48:03 GMT

I've been built same code with two different version numbers. Installed the first MSI and tried to use the second to uninstall (I was hoping that would work as the upgrade code is the same); however, I get "Another version of this product is already installed" message.

Plz help......

re: From MSI to WiX, Part 8 - Major Upgrade

DaveC4 — Wed, 22 Dec 2010 22:22:02 GMT

I've run into an interesting issue with trying to schedule REP at the end of the install. Everything works fine (as expected) when a component is being upgraded (or downgraded) in the new installer. However, if the component is unchanged, while the end result is correct (file not copied, ref count is good [during REP, the action state is the expected 'null']), the action state of the component implies the file is being installed. This means the CAs associated with the component actually get run. This is bad. (We're trying to minimize driver churn and reboots)

Is there any way to condition a CA on the true state? So far my investigation seems to indicate there isn't since the determination to not copy the file isn't actually made until the InstallFiles action in the deferred sequence.

re: From MSI to WiX, Part 8 - Major Upgrade

kit — Fri, 15 Oct 2010 16:08:56 GMT

I have the same problem :(

re: From MSI to WiX, Part 8 - Major Upgrade

Willy G — Tue, 31 Aug 2010 17:50:33 GMT

Hi Alex (or anyone that can help),

I have inserted this code into two various builds now and both still do not upgrade automatically. It throws me a message that "Another version of this product is already installed. Installation of this version cannot continue. To configure or remove..."

Can someone point me into the right direction as to what I may be missing? Thanks in advance.

re: From MSI to WiX, Part 8 - Major Upgrade

Andrey — Fri, 25 Jun 2010 03:33:29 GMT

Добрый день. Я слаб в английском, и чтоб лучше объснить суть проблем пишу на русском)

Повторяю в точность все выше описанные шаги, но мой installer ни как не хочет обновлять предыдущею версию программы. Шаги:

1. Собрал приложение в студии. Запускаю мой installer.

2. Все прекрасно устанавливается.

3. Повторно запускаю installer, мне предлагается выбрать вариант установки, Изменить, Восстановить, или Удалить. Тут все ок!

4. Если ЗАНОВО сдлеать Rebuild solution в студии(при этом НИ строчки кода НЕ менялось!!!). И снова запустить installer, то сразу же появляется окно, мол: Есть старая версия удали ее сначала плиз! :(

Another version of this product is already installed. Installation of this version cannot continue.

To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.

Вот мой код:

<?xml version="1.0" encoding="UTF-8"?>

<?define SkuName = "TestApp"?>

<?define RTMProductVersion="1.0.0" ?>

<?define ProductName="SetupProject1" ?>

<?define ProductVersion="2.0.0.0" ?>

<?define ProductCode="b7bc7c6f-9a4e-4973-be84-eca8e3427c97"?>

<?define UpgradeCode="06a81104-1e30-463d-87e1-e8a79b4c682a"?>

<?define PackageCode="{8EB1B635-E70B-4F5D-B1CE-C2B25E63A3F5}"?>

<?define Manufacturer="MyCompany"?>

<Package Id="$(var.PackageCode)" Manufacturer="$(var.Manufacturer)"

InstallerVersion="200"

SummaryCodepage='1252'

Compressed='yes'

AdminImage='no'

Platforms='Intel'

ReadOnly='yes'

ShortNames='no'

Keywords='Installer,MSI,Database'

<UpgradeVersion Minimum="$(var.ProductVersion)"

IncludeMinimum="no"

OnlyDetect="yes"

Language="1033"

Property="NEWPRODUCTFOUND" />

<UpgradeVersion Minimum="$(var.RTMProductVersion)"

IncludeMinimum="yes"

Maximum="$(var.ProductVersion)"

IncludeMaximum="no"

Language="1033"

Property="UPGRADEFOUND"/>

</Upgrade>

</Component>

</Directory>

re: From MSI to WiX, Part 8 - Major Upgrade

Cody — Tue, 08 Jun 2010 06:57:28 GMT

Alex, thanks for your reply, its realy helpful. I was wery inattentive reading this msdn article before. Also I know about UPGRADINGPRODUCTCODE property and I using it. My question was more like curiosity: I thought may be there is some little-known mechanism for such situations... well.. looks like not.

Any way thanks for you help.

re: From MSI to WiX, Part 8 - Major Upgrade

Alex Shevchuk — Mon, 07 Jun 2010 16:50:47 GMT

Hi Cody,

For your first question - quote from msdn.microsoft.com/.../aa371197(VS.85).aspx:

"The installer only runs the RemoveExistingProducts action the first time it installs a product. It does not run the action during a maintenance installation or uninstallation."

So, the answer is: there is no need to do any additional scheduling, MSI will take care of it.

As far as scheduling, it is very tricky. Even though scheduling REP after InstallFinalize is the most efficient, it may not always possible to schedule REP at this point. Sometimes you have to schedule it before InstallInitialize if there are special CA's on uninstall. Also, keep in mind that when REP uninstalls the old product, it sets UPGRADINGPRODUCTCODE property which you can use to schedule CA to run only during uninstall or during old product uninstall. This may help you in scheduling REP after InstallFinalize by splitting your CA to two separate: one for product uninstall and another one for old product uninstall during upgrade.

Hope this helps,

Alex

re: From MSI to WiX, Part 8 - Major Upgrade

Cody — Mon, 07 Jun 2010 08:08:24 GMT

Hi Alex, I have two questions for you if you please.

1. As far as we need a RemoveExistingProducts action only when we install product, don't we need some condition on it? Like "NOT REMOVE=ALL" or something like this?

2. You say that location of RemoveExistingProducts action before InstallInitialize action is inefficient and that most efficient placement for this action is after InstallFinalize action. Right? But where I must to place it if some action which deals with uninstallation(I placed them before the UnpublishComponents action) removes files, stops service, etc. I am afraid if I place RemoveExistingProducts after InstallFinalize there will be some comflicts. Can you suggest me something?