A related question: how do you support the option to change the installation
directory? I'm guessing its passed to the msi as a variable? I'm sure it's
probably easy, but my google skills are failing me :-).
Kelly
On Sep 30, 2012, at 10:02 PM, Rob Mensching wrote:
> Yes, see the WixStandardBo
That's what I figured. The installer in question is the Java Runtime. It's
pretty sparse with the command-line flags!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Best-way-to-uninstall-ExePackage-that-has-no-uninstall-flag-tp7580935p7580954.html
The version I have is 3.6.3303.0. I took a stab in the dark and rearranged
the elements various ways, but couldn't come up with a solution.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-failing-when-two-MspPackages-tp7580938p7580953.html
Sen
No. Why do you need min-max version restrictions?
Today, if you have multiple Bundles with the same UpgradeCode, the higher
version upgrades the lower versions.
You can also upgrade other Bundle's UpgradeCodes by adding a RelatedBundle
with the Action='upgrade' and the Id='UpgradeCodeOfOtherBundl
Yes I know, but I wanted to pass the value as a parameter which
should be set by Burn engine. Hence I did it that way.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Set-and-pass-a-variable-or-something-similiar-when-a-feature-is-selected-tp75799
That is the way to set a Variable in Burn. If you want to pass a Property
to an MsiPackage see the MsiProperty element.
On Fri, Sep 28, 2012 at 3:07 PM, vchauras wrote:
> look at WixBA\Bundle.wxs file where authors declare "InstallFolder" as
> string
> variable and they set that variable
> withi
You run another MSI transaction while within an MSI transaction. In WiX
v3.6 you'd probably need an executable that you can use as an ExePackage to
manage the state of that installer. That or have them fix the installer so
it can uninstall itself.
On Sun, Sep 30, 2012 at 9:08 AM, Nick Ramirez w
Hmm, could be a bug. I don't see anything in our tests that mimic that
exact behavior. What version of the WiX toolset are you using?
On Sun, Sep 30, 2012 at 12:40 PM, Nick Ramirez wrote:
> It seems that this only happens if I am installing two patches. If I
> comment
> one out and only have one
Because InstallCondition would uninstall the package when false, and you
don't want that, the engine doesn't provide built-in support for your
scenario today. Your BA, however, can override the plan for the package and
not have it install (nor uninstall anything) when the condition is false.
On Su
Yes, see the WixStandardBootstrapperApplication element.
On Sun, Sep 30, 2012 at 3:33 PM, Dave Steckler wrote:
> Looking through the archives, this has been asked a few times, but not
> answered yet, so I thought I'd ask again:
>
> Is there any relatively simple way to remove the Options button w
Looking through the archives, this has been asked a few times, but not
answered yet, so I thought I'd ask again:
Is there any relatively simple way to remove the Options button when
creating a Burn install? I'm
using WixStandardBootstrapperApplication.HyperlinkLicense, but with an
empty LicenseUrl
Just add the file to the binary table
http://wix.sourceforge.net/manual-wix2/wix_xsd_binary.htm
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Reading-a-File-in-the-MSI-tp7580942p7580943.html
Sent from the wix-users mailing list archive at Nabbl
Hi,
I'm trying to add a file (a SQL Script) to the MSI, which needs to be read in a
Custom-Action.
Alas, I can't work out where I'm going wrong here - hence this post
I ran Heat.exe to generate DBUpgrade.wxs which I then included in an existing
Wix Project:
http://schemas.microsoft.com/wix/2
Can you expand on this? I thought this was a function of the burn engine not
the BA.
(If it makes a difference this is the "SQL Server 2008 R2 SP1 Native Client"
which I only need on my client install but not if I have installed SQL Express
in the server version as SQL Express installs it.)
Ne
Try "DetectMsiFeature"
I think you need to set the requested feature state in
PlanMsiFeature
Not sure though.
Tomer...
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Detecting-Feature-state-in-Managed-BA-tp7580920p7580939.html
Sent from the w
It seems that this only happens if I am installing two patches. If I comment
one out and only have one listed in the Chain, then it gets installed okay.
The log for a good attempt, only installing one patch shows:
Verified acquired payload: Patch2.msp at path: C:\ProgramData\Package
Cache\.unverif
I have a simple Burn installer that is attempting to install two patches. The
markup is like this:
The software that it's supposed to update has been installed. If I were to
install the MSP files without using Burn, they install without a problem.
Here is what I see in the B
When your BA can't handle it.
On Sat, Sep 29, 2012 at 5:30 PM, Nick Ramirez wrote:
> I was trying out the Chain/@ParallelCache attribute and found that it
> shaved
> a second or two off of my install time. I'm sure that bigger installs would
> see more time saved. I was just wondering, is there
Correct. Your BA would need to handle that case.
On Sat, Sep 29, 2012 at 1:21 AM, Neil Sleightholm wrote:
> I have an msi in my bundle that is only installed for a particular config
> but I don't want to uninstall it if the end user has it installed. Is there
> any way to do this with the MsiPack
I've come across an executable installer that has a flag to allow it to be
installed silently. However, it doesn't have any "uninstall" flag. Its
documentation recommends that it be installed with msiexec. In these cases,
does anyone have an opinion on what the best uninstall strategy is? Should I
Okay, thanks. Next (and obvious) question then is how do I get at that file
(wherever it is) from inside the bootstrapper?
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 26. September 2012 16:30
To: General discussion for Windows Installer XML toolset.
Subjec
21 matches
Mail list logo
