Hello,
I have an installation created with InstallAware 6.6 that contains 8 features with round about 8000 files in summary, where the customer can select the features for installing. In Maintenance Mode /Modify he can add or remove features. It works, but when I select an additional feature not only this added feature will installed as expected. Features that are already installed also will be copied. For our case this is no option.
Is it right that the modify sequence is only implemented in InstallAware as described above ?
Are there any ideas to solve the problem ?
Modify will not work as expected
-
Alex_Ronquillo
- Site Admin
- Posts: 364
- Joined: Mon Jul 30, 2007 11:51 am
- Location: USA
- Contact:
I am not sure what the problem might be here, but this is something you can do. When installing, write out the components installed to a text file. On MODIFY you can read in the text file installed components, if a component is selected and it is already installed, don't install it, otherwise install it.
Alejandro Ronquillo
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
Well, I solved the problem in a similar way. The Feature Selection States will be written to registry and red back on Modify.
But I saw the script commands Load/Save FeatureSelections. In principle this script command creates already a text file with all that info you need. But the order of info is InstallAware like. May be you can parse the required info if you know how the info will be created. Currently applying of these scripts make only sense in an upgrade scenario to hold the Feature Selection States during the uninstall process and set the preselection during the subsequent install process.
It would be nice InstallAware could expand this feature for this purpose (MODIFY) or find another solution in one of the next releases.
Thanks for your quick response.
culue
But I saw the script commands Load/Save FeatureSelections. In principle this script command creates already a text file with all that info you need. But the order of info is InstallAware like. May be you can parse the required info if you know how the info will be created. Currently applying of these scripts make only sense in an upgrade scenario to hold the Feature Selection States during the uninstall process and set the preselection during the subsequent install process.
It would be nice InstallAware could expand this feature for this purpose (MODIFY) or find another solution in one of the next releases.
Thanks for your quick response.
culue
Hi, I'm evaluating InstallAware and found the same problem. The Modify doesn’t skip the already installed files, instead it just installs all the files again. so it is very slow to add or remove a new component if I already had a lot of components installed.
I thought InstallAware should support this by default. Will this be in a future release?
Thanks,
I thought InstallAware should support this by default. Will this be in a future release?
Thanks,
Well, if a component already was selected before, then ignore his block of installation commands, OK. This is easy, but what about components that were previously selected, but now have been unselected by the user? These should be removed from the installation, right? How am I supposed to implement this remotion on IA? Is this just as painful as I'm thinking it does?
Thanks in advance!
Thanks in advance!
[b]Tiago Rocha[/b]
[i]Product Technology[/i]
www.ppi-multitask.com.br
[i]Product Technology[/i]
www.ppi-multitask.com.br
Hi all,
As what Mr.Alex suggested earlier,
I wants the setup to display all the component files of the setup in the 'componentstree' dialog in order for user to choose n check the particular files that they want to install or remove from the setup....but yet, it is not executing it...Can someone pleaseeeee suggest me a solution for this?????
Eagerly waiting for a reply...
Thanks in advance..
Regards,
Serina[/code][/quote]
As what Mr.Alex suggested earlier,
Well, I would like to know where should I place the script exactly in my code?? So far this what my script looks likeWhen installing, write out the components installed to a text file. On MODIFY you can read in the text file installed components, if a component is selected and it is already installed, don't install it, otherwise install it.
Code: Select all
label: Maintenance
Comment: Maintenance Install/Uninstall
wizard loop
Display Dialog: maintenance, wait for dialog to return (modal)
Display Dialog: componentstree (if variable MODIFY is TRUE), wait for dialog to return (modal)
if Variable MODIFY Equals TRUE
Read from Text File $TARGETDIR$\\CanteenKiosk_ModifyFiles.txt into Variable COMPONENTS (get EOF into COMPONENTS)
end
Display Dialog: startinstallation, wait for dialog to return (modal)
endEagerly waiting for a reply...
Thanks in advance..
Regards,
Serina[/code][/quote]
Hi Serina,
Well, these things look a bit confusing at first sight, but this whitepaper clarifies everything: http://www.installaware.com/msicode_scr ... nology.pdf
Take a look at the A Single Script for Installs, Maintenance, and Uninstalls section at page 7 for more details.
Best Regards
Well, these things look a bit confusing at first sight, but this whitepaper clarifies everything: http://www.installaware.com/msicode_scr ... nology.pdf
Take a look at the A Single Script for Installs, Maintenance, and Uninstalls section at page 7 for more details.
Best Regards
[b]Tiago Rocha[/b]
[i]Product Technology[/i]
www.ppi-multitask.com.br
[i]Product Technology[/i]
www.ppi-multitask.com.br

