remember feature during upgrade
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?
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
Answers (20)
Please log in to answer
Posted by:
turbokitty
14 years ago
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)?
Posted by:
kiptek
14 years ago
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...
Posted by:
desert_rose
14 years ago
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
I have build both the app.
Kiptek: can you give more info about the symantec MR you have mentioned
Posted by:
kiptek
14 years ago
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.
If you built the previous package and deployed it, why not just use the same commandline switches/args and that should replicate the install.
Posted by:
anonymous_9363
14 years ago
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.
Posted by:
desert_rose
14 years ago
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
Posted by:
desert_rose
14 years ago
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
on a second note if there is a new component added to a feature. will that affect the case here
Posted by:
anonymous_9363
14 years ago
on a second note if there is a new component added to a feature. will that affect the case hereNo.
Posted by:
desert_rose
14 years ago
can someone suggest wat might be wrong here...any help is greatly appreciated.
Posted by:
anonymous_9363
14 years ago
Up until now you haven't said that anything was wrong! :)
What does a verbose log tell you? Start with that.
What does a verbose log tell you? Start with that.
Posted by:
turbokitty
14 years ago
Since you having so much fun here VBScab, I'll leave this thread for you. [:D]
Posted by:
anonymous_9363
14 years ago
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.
Have a look through it and post questions on anything that looks odd.
Posted by:
kiptek
14 years ago
and an Oracle Client to package.
Still fighting the good fight i see... or is it tilting @ windmills..? [8D]
Posted by:
turbokitty
14 years ago
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.
Posted by:
reds4eva
14 years ago
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.
Posted by:
anonymous_9363
14 years ago
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.
Posted by:
anonymous_9363
14 years ago
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...
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.