Suggested Articles
Search found 9 matches
- Tue Jan 19, 2016 4:57 pm
- Forum: Building Installers
- Topic: Set property in Powershell without literal name
- Replies: 10
- Views: 8065
- Jump to post
- Fri Jan 15, 2016 11:47 pm
- Forum: Building Installers
- Topic: Using config file with attached DLL?
- Replies: 7
- Views: 6795
- Jump to post
Re: Using config file with attached DLL?
Hi,
Indeed, the " Launch file " custom action does not work for DLL files.
So in order to get the "convenience" of the wix custom actions in a dll, we're forced to write cleanup custom actions? Some of the limitations in AI are just baffling. It's a great product right up until you cripple vital ...
Indeed, the " Launch file " custom action does not work for DLL files.
So in order to get the "convenience" of the wix custom actions in a dll, we're forced to write cleanup custom actions? Some of the limitations in AI are just baffling. It's a great product right up until you cripple vital ...
- Fri Jan 15, 2016 11:40 pm
- Forum: Building Installers
- Topic: Set property in Powershell without literal name
- Replies: 10
- Views: 8065
- Jump to post
Re: Set property in Powershell without literal name
Still need an answer to this.
- Thu Jan 07, 2016 5:13 pm
- Forum: Building Installers
- Topic: Set property in Powershell without literal name
- Replies: 10
- Views: 8065
- Jump to post
Re: Set property in Powershell without literal name
Bringing this back up because I'm having a related problem. Setting a property is no problem, but getting a property by a variable name turns out not to work. I'm running this powershell script from a custom action off a dialog, just to test the functionality.
This is an example of a line that ...
This is an example of a line that ...
- Mon Dec 28, 2015 4:12 pm
- Forum: Building Installers
- Topic: Conditioning a dialog disables Back button
- Replies: 3
- Views: 2948
- Jump to post
Re: Conditioning a dialog disables Back button
Turns out that the back (and next) buttons had been set to "disabled" in the editor. With the exception mentioned above, the back button on a conditioned dialog, they were never disabled when the install ran so I didn't notice. Anyway, setting them back to enabled fixed this issue for me.
- Wed Dec 23, 2015 9:56 pm
- Forum: Building Installers
- Topic: Conditioning a dialog disables Back button
- Replies: 3
- Views: 2948
- Jump to post
Conditioning a dialog disables Back button
Hi, not clear on what is happening here. I have a number of dialogs in my sequence. If I right click on one and choose "Show only if...", then set a valid condition, the back button on that dialog is disabled when the dialog appears. This occurs consistently with all the dialogs I've tried. There's ...
- Fri Dec 18, 2015 2:56 pm
- Forum: Building Installers
- Topic: Set property in Powershell without literal name
- Replies: 10
- Views: 8065
- Jump to post
Re: Set property in Powershell without literal name
Yes, it was the misspelling. Thank you!
- Thu Dec 17, 2015 9:07 pm
- Forum: Building Installers
- Topic: Set property in Powershell without literal name
- Replies: 10
- Views: 8065
- Jump to post
Set property in Powershell without literal name
With AI_MsiSetProperty, how can I use a variable instead of the name of the property literally spelled out in script? I need to arbitrarily set properties by name. This example fails when it calls AI_MsiSetProperty.
$propname = "FOO"
$propval = "FOOVAL"
AI_MsiSetProperty $propname $propval
Is ...
$propname = "FOO"
$propval = "FOOVAL"
AI_MsiSetProperty $propname $propval
Is ...
- Thu Dec 17, 2015 4:27 am
- Forum: Building Installers
- Topic: HTML Host with no UI
- Replies: 1
- Views: 1973
- Jump to post
HTML Host with no UI
I searched and couldn't find anything on this (not surprised, though.) Is there any way to get at this control without loading a dialog? I was considering using it to access a web page to retrieve properties from a database, but the control would never exist in silent.
(Assuming this isn't possible ...
(Assuming this isn't possible ...