This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Chained MSI Install Properties...
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 28, 2009
09:53 AM
Chained MSI Install Properties...
Using: IS 2009 Premier, Basic MSI.
I am chaining a MSI that has 2 properties, CUSTOMER_NAME, CUSTOMER_ADDRESS.
In the Install properties settings I enter the following:
CUSTOMER_NAME="[EDIT_CUSTOMER_NAME]" CUSTOMER_ADDRESS="[EDIT_CUSTOMER_ADDRESS]"
The EDIT_ properties are retrieved from my install package dialogs.
The MSI (created in Visual Studio 2009) contains the CUSTOMER_ properties. In VS these properties have default values.
In the Visual Studio CustomActionData field I have the following:
/CustomerName="[CUSTOMER_NAME]" /CustomerAddress="[CUSTOMER_ADDRESS]"
So I run the install and set the EDIT_CUSTOMER properties, however these values are not being passed to the chained MSI.
What am I doing wrong?
Thanks,
Rick
I am chaining a MSI that has 2 properties, CUSTOMER_NAME, CUSTOMER_ADDRESS.
In the Install properties settings I enter the following:
CUSTOMER_NAME="[EDIT_CUSTOMER_NAME]" CUSTOMER_ADDRESS="[EDIT_CUSTOMER_ADDRESS]"
The EDIT_ properties are retrieved from my install package dialogs.
The MSI (created in Visual Studio 2009) contains the CUSTOMER_ properties. In VS these properties have default values.
In the Visual Studio CustomActionData field I have the following:
/CustomerName="[CUSTOMER_NAME]" /CustomerAddress="[CUSTOMER_ADDRESS]"
So I run the install and set the EDIT_CUSTOMER properties, however these values are not being passed to the chained MSI.
What am I doing wrong?
Thanks,
Rick
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 28, 2009
01:21 PM
It's a little unclear from this description how far the properties make it. Let's try to answer where they fall out. Presumably if you take a verbose log of your outer installation, you'll see the EDIT_* variants get set in the dialogs. Possibly you'll see those set in the execute sequence - are they listed in the SecureCustomProperties property? Possibly you'll see them in the arguments passed to the chained install - are they listed in the IS_CHAINER_POST_COMMANDLINE property? Possibly you'd see them in a verbose log of the inner installation.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 29, 2009
12:06 PM
SecureCustomProperties = NEWERPRODUCTFOUND
IS_CHAINER_POST_COMMANDLINE has the correct values.
What is not clear to me is the following where my new values get replaced (This happens shortly after the "Running ExecuteSequence".):
Doing action: CustomTextA_SetProperty_EDIT1
Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'CustomTextA_SetProperty_EDIT1'
PROPERTY CHANGE: Modifying CUSTOMER_NAME property. Its current value is 'new name'. Its new value: 'old name'.
Rick
IS_CHAINER_POST_COMMANDLINE has the correct values.
What is not clear to me is the following where my new values get replaced (This happens shortly after the "Running ExecuteSequence".):
Doing action: CustomTextA_SetProperty_EDIT1
Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'CustomTextA_SetProperty_EDIT1'
PROPERTY CHANGE: Modifying CUSTOMER_NAME property. Its current value is 'new name'. Its new value: 'old name'.
Rick
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 30, 2009
10:15 AM
Update:
I went into the MSI setup package in Visual Studio and removed TextBoxA (the install dialog that contains CUSTOMER_NAME and CUSTOMER_ADDRESS).
Now when I run my IS chained MSI install package, the properties I set during the install interview are no longer being over-written by the chained MSI.
I would not have expected the interview content in the MSI to cause a problem for the chain install process - is this the normal behavior?
Thanks,
Rick
I went into the MSI setup package in Visual Studio and removed TextBoxA (the install dialog that contains CUSTOMER_NAME and CUSTOMER_ADDRESS).
Now when I run my IS chained MSI install package, the properties I set during the install interview are no longer being over-written by the chained MSI.
I would not have expected the interview content in the MSI to cause a problem for the chain install process - is this the normal behavior?
Thanks,
Rick