/bundles/itninjaweb/img/Breadcrumb_cap_w.png
Well, here's the case I've got.
A long time ago, I have a deployed package that installs two features from one MSI file.
Now I need to deploy a new package containing one feature that was not available on the previous release, but I cannot uninstall the previous package, I need to add the new feature and maintain those from the older one.
Can anyone advise?

Thanks in advance,
Luiz
0 Comments   [ - ] Hide Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity

Answers

0
You may create an upgrade package for the existing one.

-Sooraj
Answered 07/28/2009 by: soorajganga
Senior Yellow Belt

Please log in to comment
0
Try using Reinstallmode property and check as below.

Msiexec /i xxx.msi REINSTALL=ALL REINSTALLMODE=omus

Regards
Ramesh
Answered 07/28/2009 by: ramesh111k
Purple Belt

Please log in to comment
0
Try using Reinstallmode property and check as below.Yes, that's right...re-install a feature which doesn't yet exist. Hmmm....LOL :)

Sooraj is right. You need to create an upgrade for your product. If you're using Wise or InstallShield, this'll be a cinch.
Answered 07/29/2009 by: VBScab
Red Belt

Please log in to comment
0
But using the Upgrade, this will uninstall the previous application and install the new version, right ?

I don't think this what he want.

How about creating a .msp ?
Answered 07/29/2009 by: darkfang
Blue Belt

Please log in to comment
0
I've always found upgrade MSIs to be much more convienent in the long run than MSPs. I would recommend an upgrade MSI.
Answered 07/29/2009 by: elgwhoppo
Senior Purple Belt

Please log in to comment
0
Hi,

Thanks for your entries, but I managed to find another solution.
I am executing the msi file using the following parameters: /QB! ADDLOCAL=FeatureName
This adds the feature I want without changing the previous installation.

Thanks for your help,
Luiz
Answered 07/29/2009 by: lsilva49
Senior Yellow Belt

Please log in to comment
0
So now you have two separate products, effectively. What will you do for the next upgrade? Create yet another product? It's not a simple call, I agree, (as in, does a new feature require a new product or not?) but from what little you've told us, I'd say that the new product route was a mistake.
Answered 07/29/2009 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: VBScab

So now you have two separate products, effectively. What will you do for the next upgrade? Create yet another product? It's not a simple call, I agree, (as in, does a new feature require a new product or not?) but from what little you've told us, I'd say that the new product route was a mistake.


Hi,

If things were on my hands alone I would do something about it, but my company has a very strict packages' structure. We're unable to modify published packages and many other restrictions, but thanks for yer help.

Luiz
Answered 07/29/2009 by: lsilva49
Senior Yellow Belt

Please log in to comment
0
We're not talking about modifying the existing package. Have a browse on MSDN for details on what constitutes a 'product' and a 'package'. If you look up 'UpgradeCode', 'ProductCode' and'PackageCode', you should find plenty to keep you occupied.
Answered 07/29/2009 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: VBScab

We're not talking about modifying the existing package. Have a browse on MSDN for details on what constitutes a 'product' and a 'package'. If you look up 'UpgradeCode', 'ProductCode' and'PackageCode', you should find plenty to keep you occupied.


I already said thanks for your help and support, there is no need to be rude.
Answered 07/29/2009 by: lsilva49
Senior Yellow Belt

Please log in to comment
0
Where was I rude?!?
Answered 07/29/2009 by: VBScab
Red Belt

Please log in to comment
0
I don't want to cause a commotion around here. Let's just forget what has happened. Thanks everyone. x
Answered 07/29/2009 by: lsilva49
Senior Yellow Belt

Please log in to comment