Using WixStdBA with WiX 3.6.
Is there a way allow custom command line parameters to set values of Variables
in the bundle?
Thanks,
Ian
--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free trouble
Hi,
A user is reporting a problem with a shipped installer that my team has not
seen before. It uses a wixstdba bootstrapper to wrap several MSIs. I think the
WiX build used was from about a month or two before the WiX 3.6 Release
Candidate, though it might be a more recent build.
The user re
I'll looking to have my burn bundle invoke uninstall on a different burn bundle
if it is detected on a machine. What is the easiest way to accomplish this?
Thanks,
Ian
--
Live Security Virtual Conference
Exclusive live e
Yep, you need to reference something in a fragment (DirectoryRef, ComponentRef,
etc) to load the fragment (it will all be loaded, note).
Also remember to include allt he .wxs files in your call to candle and light.
Ian
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
esday, February 15, 2012 7:18 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bundle rollback during install is not correct
Strange. What does the plan show as the state for all these packages?
On Tue, Feb 14, 2012 at 11:41 AM, Ian Williams wrote:
> I have
I have wixstdba bundle with MSI packages A, B, C, D, E. They are all marked as
vital and the chain explicitly says DisableRollback="no". There are no
RollbackBoundary elements, either. I'm using a wix build 3.6.2527.0.
During install, if I click the cancel button during package C's installatio
Just a guess, but what is the Package/@InstallerVersion? That attribute should
be the minimum Windows Installer number required - Major*100 + Minor.
-Original Message-
From: Maxim Kopeyka [mailto:m...@xtendx.com]
Sent: Friday, February 10, 2012 8:52 AM
To: wix-users@lists.sourceforge.ne
thread.
Thanks again,
Ian
-Original Message-
From: Sam Morris [mailto:s...@red-redemption.com]
Sent: Thursday, February 09, 2012 5:07 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Localized bundle: Picking up the right files
On Thu, 09 Feb 2012 07:57:52 +0000, Ian Williams
rrect, but whenever I do
this the installer doesn't seem to work: invoking with -lang does nothing and exits immediately. Has anyone been able to load a
thm.xml per language?
Thanks,
Ian
-Original Message-
From: Ian Williams [mailto:iawil...@microsoft.com]
Sent: Wednesday, Febr
Using WixStdba.RtfLicense, I'm able to localize various strings with the .wxl.
But I'm having difficulty customizing the theme with the .xml files, and I
can't figure out how to get a different license to load for each language.
...
...
I _think_ you can accomplish everything you want here by simply passing in a
runtime property when msiexec is called, like "ConfigurationToBuild". Then you
can use the value of that property to determine what to install, etc. I've had
success with that approach personally.
-Original Message
Hi Lars,
The /quiet flag that msiexec takes when running an MSI is still valid for MSI's
build in WiX 3.6, of course. WiX 3.6 bundles are passed whatever command line
arguments you send them, so they can be made to accept /quiet as well. If
you're using WiXStdba, I can confirm that it will acce
Merging threads; just ensuring my reply doesn't get lost. Thanks.
-Original Message-
From: Ian Williams [mailto:iawil...@microsoft.com]
Sent: Monday, January 09, 2012 11:15 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Globalized Bundle?
Hmm
I believe you are mixing WiX preprocessor variables with runtime properties.
Your property IISROOT should be accessed using the following syntax: [IISROOT]
You are using the preprocessor syntax: $(var.IISROOT). Try [IISROOT] there
instead.
Ian
-Original Message-
From: Bourne, Kevin [ma
need to be fixed before this
works well but you can see the beginnings.
On Thu, Jan 5, 2012 at 2:59 PM, Ian Williams wrote:
> I'm trying to investigate the viability of making my bundle installer
> "globalized" - that is, it is one installer that will look at the
> languag
I think you meant
"ja-jp"
http://msdn.microsoft.com/en-us/goglobal/bb896001.aspx
:-)
-Original Message-
From: Nan Zang [mailto:naz...@microsoft.com]
Sent: Thursday, January 05, 2012 5:40 PM
To: General discussion for Windows Installer XML toolset.
(wix-users@lists.sourceforge.net)
Subj
I'm trying to investigate the viability of making my bundle installer
"globalized" - that is, it is one installer that will look at the language of
the system in order to choose how to present itself to the user (and perhaps
what to install). I thought that was one of the advantages of using a b
Command line variables given to the bundle are passed to the BA. The WixStdBA
currently does not turn them into variables that you can use in your bundle.
-Original Message-
From: Gilles QUERRET [mailto:g.quer...@gmail.com]
Sent: Tuesday, December 20, 2011 7:11 AM
To: wix-users@lists.s
I'm trying to present the user with some options when installing my product at
the bundle level, so I can decide which MSIs I want to run. I'm using wix3.6
with WixStdba right now. Is there any way I can keep the standard bootstrapper
and get something like selectable items? Are there any opti
I'm trying to pass variables into a burn bundle like this:
MyInstaller.exe SOME_VARIABLE=true
I found a thread saying that variables passed into a burn bundle are given to
the BootstrapperApplication, which may create variables from them. I'm using
WixStandardBootstrapperApplication.RtfLicense
ls
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
> -Original Message-
> From: Ian Williams [mailto:iawil...@microsoft.com]
> Sent: Monday, November 21, 2011 4:17 PM
> To: wix-users@lists.sourceforge.net
I'm trying to conditionally include some CustomActionRef's based on a property
at runtime. I'm on WiX 3.6 beta right now. I can't figure out how to do this.
Does anyone know if this is possible?
Thanks,
Ian
--
All the
22 matches
Mail list logo
