I now have an error in my logs much sooner in the bootstrapper process:
[1878:157C][2014-08-18T23:01:04]i001: Burn v3.8.1128.0, Windows v6.1 (Build
7601: Service Pack 1), path:
C:\5.5_tunney\Installation\Products\ExpressMBA\ExpressMBA\bin\Debug\ExpressMBA.exe,
cmdline: ''
[1878:157C][2014-08-18
Thanks, seen that one and this one
https://community.logos.com/forums/p/87997/617278.aspx. Both look similar.
Neil
-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: 18 August 2014 20:13
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] SECREPAIR: Crypt
The configuration file must be named BootstrapperCore.config. The easiest
thing to do is just add Name="BootstrapperCore.config" to the Payload of
your config file.
On Mon, Aug 18, 2014 at 1:49 PM, Tunney, Stephen
wrote:
> Hello everyone,
>
> I'm attempting to write my first bootstrapper (YAY)
Hi Rob and Bob,
Quick question.
I would like your honest opinion about changing default MSI behavior, i.e.
Upgrades by changing a WIX installer to modify its behavior to act like an
upgrade when the version number has not changed?
i.e. you have version 1.2.3.x installed and then the user upgrade
Hello everyone,
I'm attempting to write my first bootstrapper (YAY) and I've decided that the
managed bootstrapper would be ideal for our organization. I'm trying to get a
quick and dirty sample up and running with a dummy MSI inside that installs its
own WXS file.
Running WiX 3.8 RTM with VS
FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb2918614-causing-overlapped-i-o-operation-progress-errors.html
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-CryptAcquireContext-Could-not-create-the-default-key-contai
Hello,
I'm wanting to call a custom action when the installer starts up. I've added it
to the InstallUISequence as in the code below and it does get executed. The
problem is that it takes a few seconds for the custom action to run and the
hourglass/spinner either stops when I call the custom a
Has anyone seen the issue below?
We are deploying MSIs via a remote PowerShell script and last week it suddenly
started failing with this error. We have tracked the problem down to Hotfix
2918614 (released 12 Aug 2014) but were curious if anyone else is experiencing
the problem or know what is
I'm not sure if Neil's contributions to WixStdBA would allow you to property
drive a variable from the modify/uninstall page. If they do, it would simply
mean a need for a custom theme file with the check box added to the page, a
variable associated with the check box, and a MsiProperty element
I'm using WiX 3.8 to create a Boot Strapper and have added a new EditBox to
the Options page, to allow the user to enter a database instance name and I
use this to install SQL Express 2014 and create an instance for the user.
This works fine !
In bundle.wxs :
In my Theme xml file, for th
Have you tried putting conditions in your ?
http://alekdavis.blogspot.com/2013/05/wix-woes-what-is-your-installer-doing.html
- NOT Installed OR REINSTALL
InstallUninstallRepairModifyUpgradeINSTALLEDFALSETRUEFALSETRUETRUEREINSTALL
TRUEFALSETRUEFALSEFALSEREMOVE="ALL"FALSETRUEFALSETRUETRUE
U
its an issue where I am using burn to bundle my msi and payload files
together and my msi has a checkbox option when a uninstall is triggered and
if the checkbox is ticked sends a variable to the msi during uninstall to
drop databases, however I am not sure this is possible with the standard or
eve
I have some files that I don not want to be removed when uninstalling but I
want to be reinstalled when the installation is repaired. So far I have
tried various combinations of setting the component to permanent, setting
NeverOverwrite to no, setting REINSTALLMODE to amus, leaving the component
gu
13 matches
Mail list logo
