I've created a test project and added the following features to it. All features are initially selected:
Define Component: A
Define Component: A\B
Define Component: A\C
Define Component: A\C\D
Define Component: A\C\E
Define Component: F
Define Component: G
Define Component: G\H
Define Component: G\I
I then created this code that responds to the feature selections made and it does nothing more than display a message box if the feature is selected:
[OFFLINE CONTENT]
[DEFINE WEB MEDIA A]
Get Component A Selection State into Variable SELECTED
if Variable SELECTED Equals TRUE
MessageBox: , A
end
[DEFINE WEB MEDIA AB]
Get Component A\B Selection State into Variable SELECTED
if Variable SELECTED Equals TRUE
MessageBox: , A\B
end
[DEFINE WEB MEDIA AC]
Get Component A\C Selection State into Variable SELECTED
if Variable SELECTED Equals TRUE
MessageBox: , A\C
end
[DEFINE WEB MEDIA ACD]
Get Component A\C\D Selection State into Variable SELECTED
if Variable SELECTED Equals TRUE
MessageBox: , A\C\D
end
[DEFINE WEB MEDIA ACE]
Get Component A\C\E Selection State into Variable SELECTED
if Variable SELECTED Equals TRUE
MessageBox: , A\C\E
end
[DEFINE WEB MEDIA F]
Get Component F Selection State into Variable SELECTED
if Variable SELECTED Equals TRUE
MessageBox: , F
end
[DEFINE WEB MEDIA G]
Get Component G Selection State into Variable SELECTED
if Variable SELECTED Equals TRUE
MessageBox: , G
end
[DEFINE WEB MEDIA GH]
Get Component G\H Selection State into Variable SELECTED
if Variable SELECTED Equals TRUE
MessageBox: , G\H
end
[DEFINE WEB MEDIA GI]
Get Component G\I Selection State into Variable SELECTED
if Variable SELECTED Equals TRUE
MessageBox: , G\I
end
If I run the setup and select the Compact installation then all the message boxes are correctly displayed except the first one for feature A. I was expecting A's message box to be displayed as well. Is this correct behaviour? It displays the message boxes for F and G which are at the same node level as A.
IA10: features.
IA10: features.
Peter. Smartly dressed, he still resembles an unmade bed.
InstallAware MVP
InstallAware MVP
Re: IA10: features.
That doesn't seem right. Did you build this in IA 10? How did you create your project? I tested from a blank setup and could not reproduce.
Does the attached project exhibit the same problem for you? Can you post the test project you created?
Does the attached project exhibit the same problem for you? Can you post the test project you created?
- Attachments
-
- FeaturesFromBlank.7z
- (538 Bytes) Downloaded 358 times
Andy Mills
InstallAware
Other Help:
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help - Press F1 in the InstallAware IDE.
InstallAware
Other Help:
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help - Press F1 in the InstallAware IDE.
-
ramil.domingo
- Posts: 3
- Joined: Tue Sep 28, 2010 2:36 am
Re: IA10: features.
First and foremost, my apologies for the long post.
We have encountered the same problem with IA 10. The blank project that you supplied is incomplete in order to reproduce the problem.
Here are the steps to reproduce this problem.
1. Create a blank project with multiple nested features in the list.
i.e.
[A]
[A]\[A1]
[A]\
[A]\\[C]
[A]\\[C]\[C1]
[A]\\[C]\[C2]
[A]\\[D]
[A]\\[D]\[E]
Where:
[A] = Selected
[A1] = Selected
= Selected
[C] = Selected
[C1] = Selected
[C2] = Selected
[D] = Unselected
[E] = Unselected
2. Set the following Compiler Variables.
LOADOLDDATA = TRUE
CACHESOURCES = TRUE
3. Call the Load Feature Selection command before the User Interview region and store it to $SFXPATH$\SetupChoices.txt
4. Call the Save Feature Selection command before the Apply Patch command and store it to $TARGETDIR$\SetupChoices.txt.
5. Add 1 txt file to components [A], [A1] and . Make sure they are under their own Web Media Block.
6. Rebuild and Run the installer.
7. From the Component Feature wizard page, Unselect the component , leaving you only [A] and [A1] as the selected features to be installed.
8. You will then notice once the Apply Install is called, components [A] and [A1] are extracted and files are copied to the target directory BUT component is also being installed even though you have unselected it from step #7 above. This is where the problem is coming from because it throws an error that the file is missing during an install of an UNSELECTED feature component.
Please help. We are trying to roll out a release this week and this is what's keeping us from doing so.
Thank you in advance.
We have encountered the same problem with IA 10. The blank project that you supplied is incomplete in order to reproduce the problem.
Here are the steps to reproduce this problem.
1. Create a blank project with multiple nested features in the list.
i.e.
[A]
[A]\[A1]
[A]\
[A]\\[C]
[A]\\[C]\[C1]
[A]\\[C]\[C2]
[A]\\[D]
[A]\\[D]\[E]
Where:
[A] = Selected
[A1] = Selected
= Selected
[C] = Selected
[C1] = Selected
[C2] = Selected
[D] = Unselected
[E] = Unselected
2. Set the following Compiler Variables.
LOADOLDDATA = TRUE
CACHESOURCES = TRUE
3. Call the Load Feature Selection command before the User Interview region and store it to $SFXPATH$\SetupChoices.txt
4. Call the Save Feature Selection command before the Apply Patch command and store it to $TARGETDIR$\SetupChoices.txt.
5. Add 1 txt file to components [A], [A1] and . Make sure they are under their own Web Media Block.
6. Rebuild and Run the installer.
7. From the Component Feature wizard page, Unselect the component , leaving you only [A] and [A1] as the selected features to be installed.
8. You will then notice once the Apply Install is called, components [A] and [A1] are extracted and files are copied to the target directory BUT component is also being installed even though you have unselected it from step #7 above. This is where the problem is coming from because it throws an error that the file is missing during an install of an UNSELECTED feature component.
Please help. We are trying to roll out a release this week and this is what's keeping us from doing so.
Thank you in advance.
Re: IA10: features.
Andy, I'm inclined to think it was my snafu. I've since deleted that project and recreated it and what I was testing came right.mills wrote:That doesn't seem right. Did you build this in IA 10? How did you create your project? I tested from a blank setup and could not reproduce.
Does the attached project exhibit the same problem for you? Can you post the test project you created?
Peter. Smartly dressed, he still resembles an unmade bed.
InstallAware MVP
InstallAware MVP
Re: IA10: features.
I couldn't reproduce Ramil's claim. What template did you start with? Are you using NATIVE_ENGINE? Could you post a sample project?
Andy Mills
InstallAware
Other Help:
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help - Press F1 in the InstallAware IDE.
InstallAware
Other Help:
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help - Press F1 in the InstallAware IDE.

