Go Back   PackageDeploy Application Packaging Forums > Package Development > Application Packaging > Windows MSI

Reply
 
LinkBack Thread Tools Display Modes
Old 03-15-2010, 06:54 PM   #1 (permalink)
Fyodor Koryazhkin
Guest
 
Posts: n/a
Default Multi instance upgrade

Hi everybody,
The MSDN documentation says that to create multi instance installation
the instance transforms that change product code should be used and
actually this should be sufficient. But following this scenario I have a
problem on major upgrade.
Let say I have two instances installed on the computer and want to
update one of them using major upgrade. The first release uses one
upgrade code and two instance transforms that actually change product codes.

In the second release I populate Upgrade table with the upgrade code of
the first release and during the run of FindRelatedProducts action the
ActionProperty is filed with two products codes of two instances of
first release. Thus the action RemoveExistingProducts removes two
instances of the first release.

The question is how to avoid removing the second instance?

Thank you.
  Reply With Quote
Old 03-15-2010, 06:54 PM   #2 (permalink)
Adrian Accinelli
Guest
 
Posts: n/a
Default Re: Multi instance upgrade

"Fyodor Koryazhkin" <fyodorkor@gmail.com> wrote in message
news:unyBg%23kuKHA.4492@TK2MSFTNGP05.phx.gbl...
> Hi everybody,
> The MSDN documentation says that to create multi instance installation the
> instance transforms that change product code should be used and actually
> this should be sufficient. But following this scenario I have a problem on
> major upgrade.
> Let say I have two instances installed on the computer and want to update
> one of them using major upgrade. The first release uses one upgrade code
> and two instance transforms that actually change product
> codes.
> In the second release I populate Upgrade table with the upgrade code of
> the first release and during the run of FindRelatedProducts action the
> ActionProperty is filed with two products codes of two instances of first
> release. Thus the action RemoveExistingProducts removes two instances of
> the first release.
> The question is how to avoid removing the second instance?
> Thank you.


Did you try modifying the ActionProperty value so that it only has the
ProductCode of the instance you want to remove? If you do this before
RemoveExistingProducts action is scheduled it shouldn't know about the
second instance and thus not act upon it.

Sincerely,
Adrian Accinelli


  Reply With Quote
Old 04-04-2010, 03:01 AM   #3 (permalink)
hixxxej
Guest
 
Posts: n/a
Default Re: Multi instance upgrade

Your system does not have ActiveX installed. It was sold entirely to Adobe
Inc. Call them! (not the macromedia team)

"Fyodor Koryazhkin" <fyodorkor@gmail.com> wrote in message
news:unyBg%23kuKHA.4492@TK2MSFTNGP05.phx.gbl...
> Hi everybody,
> The MSDN documentation says that to create multi instance installation the
> instance transforms that change product code should be used and actually
> this should be sufficient. But following this scenario I have a problem on
> major upgrade.
> Let say I have two instances installed on the computer and want to update
> one of them using major upgrade. The first release uses one upgrade code
> and two instance transforms that actually change product codes.
>
> In the second release I populate Upgrade table with the upgrade code of
> the first release and during the run of FindRelatedProducts action the
> ActionProperty is filed with two products codes of two instances of first
> release. Thus the action RemoveExistingProducts removes two instances of
> the first release.
>
> The question is how to avoid removing the second instance?
>
> Thank you.


  Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 12:17 PM.


vBulletin, Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
2007 - 2012 PackageDeploy.com