I have checked on a clean VM and the log starts "=== Verbose logging started"
but no property dump - is the level in the log file somewhere? This doesn't
just happen with my own MSIs it happens with Microsoft ones as well.
Unfortunately I have deleted my VS2012 logs so can't check them.
Neil
-
You have the ProductCode for all the MSIs, so you can call the MSI APIs to
get more information about the product if desired.
On Thu, Nov 22, 2012 at 9:31 AM, Stelios Kyprou wrote:
> Is there a way to detect the install location of an already installed
> package via the bootstrapper application
You'd need to recreate the meta-data the bundle needs when changing the
chain anyway. Since the Burn executable engine is ~300K there was little
advantage to updating the metadata but not just stick the engine back on
the metadata again. Plus, if there is a bug in the engine, an update can
fix it.
Burn always sets verbose logging and will set extra logging if you set
extra logging in the MSI Logging registry key. I don't know why the
property dump wouldn't show up...
On Thu, Nov 22, 2012 at 8:58 AM, Neil Sleightholm wrote:
> What level of logging does burn use when installing MSIs? I have
That should be it.
On Thu, Nov 22, 2012 at 1:28 PM, Wesley Manning wrote:
> Hi,
>
> What do I need to do to create an add-on bundle?
>
> I see Rob Mensching talked about it here for a patch:
> http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg49558.htmlwhere
> he said:
> "... in t
There was a bug around cancel in wixstdba that was fixed in WiX v3.7 RC.
Might be related.
On Thu, Nov 22, 2012 at 10:03 AM, vasjko wrote:
> Any ideas on this?
>
> 22.11.2012 15:12, vasjko
> >Hi,
> >
> > I have a custom bundle which is used like prerequisite for my MBA. It
> installs some comp
Not sure. Does it repro with build 3.6.3303?
-Original Message-
From: Adrian Gantoi [mailto:gantoiadr...@yahoo.com]
Sent: Friday, November 23, 2012 3:00 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Burn on Windows 8
Hi all,
We are using a debug build
Hi all,
We are using a debug build of WiX 3.6.3005 with a few changes compared to
standard source files
and have a problem on Windows 8 only with our bundle (managed UI).
After everything is installed (or uninstalled), the chainer seems to hang for
some time, and after a couple of minutes it sho
I found that accessing the timestamp servers was more reliable when using the
actual IP address for the timestamp server (i.e. a.b.c.d notation) rather than
the hostname. Doing so eliminates DNS failures and resulted in far fewer build
failures in my case (I sign a lot of components, not just th
One other failure to watch out for when signing is that the timestamp servers
are not 100% reliable, I have a retry for those failures as well.
Neil
-Original Message-
From: Parkes, Kevin [mailto:kevin.par...@wacom.eu]
Sent: 23 November 2012 16:50
To: wix-users@lists.sourceforge.net
Sub
Liberally adding sleeps hasn't completely fixed it but seems to have reduced
the frequency of build failures to something I can probably live with
Thanks
Kev
-Original Message-
Date: Tue, 20 Nov 2012 21:57:17 +
From: Neil Sleightholm
Subject: Re: [WiX-users] Bundle signing
To: Gene
I'd recommend running the SQL install from a batch file to start with to get
the command line correct and then plug that in to burn. The command line
reference is here: http://msdn.microsoft.com/en-us/library/ms144259.aspx
My command lines are:
InstallCommand="/ACTION=Install /INSTANCENAME=$
1. Making dual-purpose packages was difficult in MSI before version 5. At my
company, we still need to support Windows prior to Windows 7/Server 2008 so
MSI 5 isn't an option yet and we create per-machine installers. With MSI 5,
dual purpose packages are easier to create:
http://msdn.microsoft.com
I have got in extracting using this:
StrAlloc(&pwzFilename, MAX_PATH);
ExitOnFailure(hr, "Failed to allocate temporary path");
::GetTempPathW(MAX_PATH, pwzFilename);
hr = ::StringCchCatW(pwzFilename, MAX_PATH, pwzBinary);
ExitOnFailure(hr, "Failed to append filename.");
I've found me an answer to fourth question. Still hoping for answers
to other questions. If I'm asking the wrong questions please tell me.
On Sat, Nov 17, 2012 at 1:29 PM,
wrote:
> Date: Fri, 16 Nov 2012 17:54:45 +0100
> From: Mihajlo Cvetanovi?
> Subject: [WiX-users] Best common practices and m
Hello,
I am trying to use the new ‘Burn’ feature for installing my application.
I need to install ‘SQL Server Express 2012’ before installing my
application. Hence, I am putting it as a prerequisite. My code is as
follows:
Hello,
From my setup I need to create a SQL Server database. I am taking a SQL
Server instance name, username and password from the user. I then try to
create the SQL database as below:
NOT PRODUCTFOUND
But, I am getting
Hi
I'd like to create my own UI for my bootstrapper.
There is no documentation about it, neither a template project in the VS
new projects
I am doing so:
-download wix3.6 source code
-compiling wixstdba from source code
-using it:
with some Payloads (pngs, xml, wxl...)
My two questions are:
-Am
Hi,
I have written a ManagedBootstrapperApplication that requires .net 4.0.
On Windows 2003 and XP, this requires the Windows Imaging Component, so
I've used another Burn bootstrapper to install the appropriate
prerequisites as per this post:
http://windows-installer-xml-wix-toolset.687559.n2.nab
Thanks for your reply,
The self-updating bundle seems interesting and I will look more into that.
I understand you advise against swapping out the MSIs on the server. The
problem with adding patches as you describe is that we already have our own
software that updates the applications we install
20 matches
Mail list logo
