-----Original Message-----
From: [email protected]
[mailto:[email protected]]
Sent: Friday, August 22, 2014 6:38 AM
To: [email protected]
Subject: WiX-users Digest, Vol 99, Issue 46
Send WiX-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/wix-users
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific than "Re:
Contents of WiX-users digest..."
Today's Topics:
1. Re: Dynamic dialog workflow (David G. van Hoose)
2. Re: Leave components installed between upgrades -but not
permanent? (Spud)
3. Re: Burn not show installed prerequisites (LocalDB) MSI in
Program and Features (Spud)
4. Re: Antivirus is blocking execution of standard bootstrapper
application (Spud)
5. Re: Burn not show installed prerequisites (LocalDB) MSI in
Program and Features (Mrugesh Patel)
6. Re: Download and Install Selected Msi packages using custom
bootstrapper (Saravanan)
7. How to display uninstall progress bar using BootStrapper
Application (linos)
8. How to reference variables within an msi that are set in
bootstrapper app (linos)
9. Re: How to reference variables within an msi that are set in
bootstrapper app (John Cooper)
----------------------------------------------------------------------
Message: 1
Date: Thu, 21 Aug 2014 16:26:21 -0500
From: "David G. van Hoose" <[email protected]>
Subject: Re: [WiX-users] Dynamic dialog workflow
To: <[email protected]>
Message-ID: <323A95C266EC4840BFEDF9148A81B40D@Bahamut>
Content-Type: text/plain; charset="UTF-8"
Hello,
I finally figured it out. I had >< instead of <> in my inequality conditions.
Orca for the win!
Regards,
David
From: David G. van Hoose
Sent: Wednesday, August 20, 2014 14:31
To: [email protected]
Subject: Dynamic dialog workflow
Hello,
I have read through lots of documentation and examples over the last year and
have made a nice web service installer. Originally, my users (web server
admins) wanted to be able to specify existing web sites during installation, so
I made custom (Internal UI) dialogs and some custom actions that communicate
with the Server Manager. Now, some of the admins want the installer to create
new application pools and web sites instead of using existing ones. My first
thought was to employ mux conditions on my PushButton?s published NewDialog
events, but those do not work.
Using the Internal UI, is there a way to have the workflow progress to
different dialogs based on the value of a ComboBox property?
If not, what alternatives would be my best options for a dynamic dialog
workflow?
Regards,
David
------------------------------
Message: 2
Date: Fri, 22 Aug 2014 03:24:16 -0700 (PDT)
From: Spud <[email protected]>
Subject: Re: [WiX-users] Leave components installed between upgrades
-but not permanent?
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Thanks for the reply (Schedule major upgrade late and ensure Component Rules
are followed. ) Rob.
I'm not sure I follow.
Hopefully I'm following the component rules as all resources used more than
once are only installed via one MSI in the GAC - lets call it
SharedComponents.msi.
In my (simplified) chain, I have
-ProductA.msi
-ProductB.msi
-ProductC.msi
-SharedComponents.msi.
SharedComponents.msi gets installed when either product A,B or C are installed.
If I schedule a major upgrade late (schedule RemoveExistingProducts after
InstallFinalize) and define the MsiPackage in the chain with a DownloadURL,
will this effectively
a) Skip downloading the SharedComponents.msi as it will already be in the cache
b) run but ultimately leave the resources untouched as it would (usually) have
no updates and no removals due to being the same MSI ?
Thanks again.
Sorry if this is a silly Q - the problem I have is that we generally only have
to update our installers every 6-8 months, by which time I've forgotten
everything <sheepish grin>.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Leave-components-installed-between-upgrades-but-not-permanent-tp7596436p7596468.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------
Message: 3
Date: Fri, 22 Aug 2014 03:29:19 -0700 (PDT)
From: Spud <[email protected]>
Subject: Re: [WiX-users] Burn not show installed prerequisites
(LocalDB) MSI in Program and Features
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
If I understand your situation correctly, the MsiPackage element in your chain
should have a Visible property. simply set this to "yes".
>From the docs:
Specifies whether the MSI will be displayed in Programs and Features (also
known as Add/Remove Programs). If "yes" is specified the MSI package
information will be displayed in Programs and Features. The default "no"
indicates the MSI will not be displayed.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-not-show-installed-prerequisites-LocalDB-MSI-in-Program-and-Features-tp7596466p7596469.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------
Message: 4
Date: Fri, 22 Aug 2014 03:33:31 -0700 (PDT)
From: Spud <[email protected]>
Subject: Re: [WiX-users] Antivirus is blocking execution of standard
bootstrapper application
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Which AV software is doing this?
We're currently not signing, so by the sounds of things may be lucky to have
not come across this.
Knowing which AV has this behaviour would be very handy.
Thanks
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Antivirus-is-blocking-execution-of-standard-bootstrapper-application-tp7596457p7596470.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------
Message: 5
Date: Fri, 22 Aug 2014 04:26:34 -0700 (PDT)
From: Mrugesh Patel <[email protected]>
Subject: Re: [WiX-users] Burn not show installed prerequisites
(LocalDB) MSI in Program and Features
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Thanks,
It's work great. You are save my lot's time. Thanks a lot.
Mrugesh Patel
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-not-show-installed-prerequisites-LocalDB-MSI-in-Program-and-Features-tp7596466p7596471.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------
Message: 6
Date: Fri, 22 Aug 2014 05:17:27 -0700 (PDT)
From: Saravanan <[email protected]>
Subject: Re: [WiX-users] Download and Install Selected Msi packages
using custom bootstrapper
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hi Rob,
Thanks for the help. It works! I have changed the RequestState to None, if the
package not selected for installation.
Is the same concept work for unisntallation? If launch from ARP, I would like
to uninstall only the selected packages and ARP entry don't get remove untill I
will uninstall all remainging platforms.
Is it possible?
Thanks,
Saravanan
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Download-and-Install-Selected-Msi-packages-using-custom-bootstrapper-tp7596433p7596472.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------
Message: 7
Date: Fri, 22 Aug 2014 05:23:29 -0700 (PDT)
From: linos <[email protected]>
Subject: [WiX-users] How to display uninstall progress bar using
BootStrapper Application
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hello,
I have a bootstrapper application (BA) that installs an MSI. Upon
installation, I have DisplayInternalUI="yes", which seems to work by displaying
the msi dialog. Now, when I perform an uninstall, through the BA, I do not see
the progress bar displaying the uninstallation. Can this be achieved using ver
Wix3.8?
Important Note: When I install my application via the msi, I see my dialog and
when I uninstall I see the progress bar.
Thanks InAdvance.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-display-uninstall-progress-bar-using-BootStrapper-Application-tp7596473.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------
Message: 8
Date: Fri, 22 Aug 2014 06:28:32 -0700 (PDT)
From: linos <[email protected]>
Subject: [WiX-users] How to reference variables within an msi that are
set in bootstrapper app
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
How can I reference in my MSI a variable that I'm passing in from my
bootstrapper. For example, I have the following text in my bundle.wxs file:
within Bundle
<Variable Name="baVersion" bal:Overridable ="yes" Type ="string" Value
="123456789"/> within MsiPackage <MsiProperty Name ="baVersion" Value
="[baVersion]"/>
In my MSI where ever I have $(var.msiVersion) I would like to use the
Msiproperty variable baVersion from my BA bundle.wxs. Is this possible?
Examples are greatly appreciated.
Thanks InAdvance
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-reference-variables-within-an-msi-that-are-set-in-bootstrapper-app-tp7596474.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------
Message: 9
Date: Fri, 22 Aug 2014 13:37:57 +0000
From: John Cooper <[email protected]>
Subject: Re: [WiX-users] How to reference variables within an msi that
are set in bootstrapper app
To: General discussion about the WiX toolset.
<[email protected]>
Message-ID:
<efe431ab7973e94a8282d4ac95ffec8055359...@mmoex10mbs02.jhacorp.com>
Content-Type: text/plain; charset="iso-8859-1"
Pass them as public properties to the MSI. From one of my bundles:
<MsiPackage Id="SomeProduct" Compressed="yes"
SourceFile="$(var.SomeProduct.TargetPath)" Vital="yes">
<MsiProperty Name="ACCOUNT_NAME" Value="[AccountName]" />
* * *
</MsiPackage>
--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.?
Shawnee Mission, KS? 66227
Office:? 913-341-3434 x791011
[email protected]
www.jackhenry.com
-----Original Message-----
From: linos [mailto:[email protected]]
Sent: Friday, August 22, 2014 8:29 AM
To: [email protected]
Subject: [WiX-users] How to reference variables within an msi that are set in
bootstrapper app
How can I reference in my MSI a variable that I'm passing in from my
bootstrapper. For example, I have the following text in my bundle.wxs file:
within Bundle
<Variable Name="baVersion" bal:Overridable ="yes" Type ="string" Value
="123456789"/> within MsiPackage <MsiProperty Name ="baVersion" Value
="[baVersion]"/>
In my MSI where ever I have $(var.msiVersion) I would like to use the
Msiproperty variable baVersion from my BA bundle.wxs. Is this possible?
Examples are greatly appreciated.
Thanks InAdvance
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-reference-variables-within-an-msi-that-are-set-in-bootstrapper-app-tp7596474.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are
intended exclusively for the individual or entity to which it is addressed. The
message, together with any attachment, may contain confidential and/or
privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message in
error, please immediately advise the sender by reply email and delete all
copies.
------------------------------
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
------------------------------
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
End of WiX-users Digest, Vol 99, Issue 46
*****************************************
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
