I am upgrading my application by installing the newer version over the already installed version.

My application give options to select different features during the installation. I want that the features that were selected during the previous installation should appear automatically selected during the upgrade installation.

what is the best possible approach to achieve this?
0 Comments   [ + ] Show 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.

Answers

0
When you say "over the already installed version" do you mean a minor or major upgrade? Or are you <shudder> abandoning the old install and laying your new "version" on top (ie. new upgrade and product codes)?
Answered 08/14/2009 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
0
I am upgrading my application by installing the newer version over the already installed version.

My application give options to select different features during the installation. I

Did you build both apps or just the upgrade? If both, did you follow best practices in creating the upgrade? Is the feature set the same? Vendors have bee known to change feature sets. Just look at the Symantec SEP 11 MR4 upgrade from MR2...
Answered 08/14/2009 by: kiptek
Second Degree Green Belt

Please log in to comment
0
its a major upgrade. upgrade code is same and product code is changing.

I have build both the app.

Kiptek: can you give more info about the symantec MR you have mentioned
Answered 08/14/2009 by: desert_rose
Orange Belt

Please log in to comment
0
The SEP issue was just an example and will probably confuse the issue right now.

If you built the previous package and deployed it, why not just use the same commandline switches/args and that should replicate the install.
Answered 08/14/2009 by: kiptek
Second Degree Green Belt

Please log in to comment
0
Those features whose names persist in the new version will be migrated. This is what the MigrateFeatureStates action does. And remember that 'Feature1' isn't the same feature as 'FEATURE1'. Microsoft (actually, Wise) went all Unix-y on us for a moment and now we have to live with it.
Answered 08/14/2009 by: VBScab
Red Belt

Please log in to comment
0
While creating the upgrade, i have checked the box saying Migrate feature states. Do i need to do anything else apart from this so that the features that were selected during the previous install are selected automatically
Answered 08/16/2009 by: desert_rose
Orange Belt

Please log in to comment
0
Yes. The feature names need to be identical, case-wise.
Answered 08/17/2009 by: VBScab
Red Belt

Please log in to comment
0
there is no change in the feature name..

on a second note if there is a new component added to a feature. will that affect the case here
Answered 08/17/2009 by: desert_rose
Orange Belt

Please log in to comment
0
on a second note if there is a new component added to a feature. will that affect the case hereNo.
Answered 08/17/2009 by: VBScab
Red Belt

Please log in to comment
0
can someone suggest wat might be wrong here...any help is greatly appreciated.
Answered 08/17/2009 by: desert_rose
Orange Belt

Please log in to comment
0
Up until now you haven't said that anything was wrong! :)

What does a verbose log tell you? Start with that.
Answered 08/17/2009 by: VBScab
Red Belt

Please log in to comment
0
is there a way to attach log file
Answered 08/17/2009 by: desert_rose
Orange Belt

Please log in to comment
0
Since you having so much fun here VBScab, I'll leave this thread for you. [:D]
Answered 08/17/2009 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
0
i welcome you both to answer this
Answered 08/17/2009 by: desert_rose
Orange Belt

Please log in to comment
0
My answer for the moment would have to be that you'd be best advised to start looking at it yourself. I have a client who pays my bills and an Oracle Client to package. Consequently, I really don't have time to trawl through your log file.

Have a look through it and post questions on anything that looks odd.
Answered 08/17/2009 by: VBScab
Red Belt

Please log in to comment
0
and an Oracle Client to package.

Still fighting the good fight i see... or is it tilting @ windmills..? [8D]
Answered 08/17/2009 by: kiptek
Second Degree Green Belt

Please log in to comment
0
VBScab, I've been using the native Oracle installer lately with good success. I recommend you give it a try. I've documented in the Packaging KB how to wade through the messy syntax or send me a PM.
Answered 08/17/2009 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
0
How can a company that is so sucessful have writteen such a poo installer. And why have they not taken on MSI. Re-packaging Orashite into MSI isnt as hard as people make it out to be.
Answered 08/17/2009 by: reds4eva
Second Degree Blue Belt

Please log in to comment
0
And why have they not taken on MSI. It's because the installer is written in Java, meaning that the same installer can be used on all their target platforms.
Answered 08/18/2009 by: VBScab
Red Belt

Please log in to comment
0
VBScab, I've been using the native Oracle installer lately with good success. I recommend you give it a try.I would normally wrap the OUI, too, but the last four releases (not mine) have been captured and we decided to be consistent. The added joy is that installing the 'Runtime' flavour of 11g causes WPS's SetupCapture to do its usual trick when faced with too many registry entries: exit, with no error message. Thank heaven for that copy of InstallShield I keep in a VM snapshot...
Answered 08/18/2009 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity