For now you could workaround this perf bug by creating a self extracting
zip file that runs the exe after extracting itself. This way Burn only has
to verify one file. 7zip is a free tool that can create that kind of zip
file.
On Fri, Feb 20, 2015 at 4:38 PM, Rob Mensching wrote:
> Or help get
It's all there in the log about what's going on.
Condition 'VersionNT>=v6.0 AND NOT VersionNT64 AND UserLanguageID <> 1034
AND UserLanguageID <> 1046 AND UserLanguageID <> 2070' evaluates to false.
Plan disabled rollback for package: TESTx86, due to incomplete cache: None,
original rollback actio
Or help get the bug fixed...
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: ctludlow [mailto:cludl...@gmail.com]
Sent: Friday, February 20, 2015 2:32 PM
To: wix-users@lists
Thanks Phill, I tried your recommendation of defaulting to cache=yes and
added the ParallelCache to the chain, but Burn just seems to take forever
verifying and copying the 3600 files still. I think I'm going to have to
abandon Burn and just write a C# app to execute the 3 setup packages
sequent
You might get some benefit from Chain/@ParallelCache='yes'. Also as I
understand it SuppressSignatureVerification="yes" is the default (assuming
wix 3.9) and there is a joy-of-setup blog somewhere which recommends to
leave options like MsiPackage/@Cache for wix to manage unless you
specifically ha
We were human:
DisableRepair YesNoType This attribute has been deprecated.
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Marco Tognacci [mailto:mark...@li
But in this case why there is the option in the Burn Bundle project?Even if it
doesn't works?
> From: r...@firegiant.com
> To: wix-users@lists.sourceforge.net
> Date: Fri, 20 Feb 2015 19:47:44 +
> Subject: Re: [WiX-users] WiX Burn Can't make appear all Uninstall - Modify
> - Repair
ARP decided that only MSIs get a "Repair" button. Definitely a bug. Can you
file it against Windows?
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Marco Tognacci [mailto:m
That perf problem is a known bug in Burn.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: ctludlow [mailto:cludl...@gmail.com]
Sent: Friday, February 20, 2015 11:24 AM
To:
Thanks for your reply Rob, I did some analysis:
Of the 3 chained exepackages I am installing, 1 sticks out like a sore thumb
because it has so many files in it.
It has 3600 files (mostly small ones) and is a total of 146mb in size.
Further analysis of the log file shows that Verifying these 3600 f
I have made a Burn setup, setting the parametersDisableUnistall="no"
DisableModify="no" DisableReapir="no"I have expected to see all three buttons
on the unistall programs system window, but only Unistall and Change appear (no
Reapir)Is this a bug? How can I make it working?
Thanks.
If verifying using signatures, could be internet connectivity latency/issues.
___
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: ctludlow [mailto:cludl...@gmail.com]
Sent: Frida
None of the boxes I install on have internet connectivity. Is that a
problem? I also have made attempts to go to the hash verification.
>From my attached project, here are examples from my Heat generated Payload
group:
--
View this message in context:
http://windows-
I don't understand what causes this error in visual studio 2008.
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactiv
I have written a bootstrap project that chains 3, 3rdParty installers
together. All 3 installers are executed and install fine by Burn, so this
is good.
The problem I'm having is the incredibly slow performance of the "Verified
existing payload:" section in the logs, before the files are actual
You can use XSLT transfroms to do that.
Then on heat.exe command line add *-t MyXsl.xslt*
The XSLT file should take this form:
http://www.w3.org/1999/XSL/Transform";
xmlns:wix="http://schemas.microsoft.com/wix/2006/wi";
xmlns:msxsl="urn:schemas-microsoft-com:xslt"
exclude-resu
Hello,
I have problem with burn. When i upgrade burn and if i do cancel and then again
perform upgrade then Burn uninstall msi and then install msi.
Steps are below:
Step1: Install older version 1.0
Step2: Upgrade with new version 1.1 and when Burn display click on cancel.
Step3: Run setup again
17 matches
Mail list logo