I think what you're missing is that you're assuming every package in the chain
has a user interface. My typical installer has my application MSI, and at
least one prerequisite (i.e. .NET). I want the bootstrapper to silently
install the prerequisites, and only show UI for the MSI. Once the bo
Hi all,
A few questions regarding the Wix Standard Bootstrapper:
1. Is there a way to tell the Burn engine to not log the command line passed
to the bundle?
E.g. If I run my bundle with the following command
MyBundleInstaller.exe Parameter=Value
The first line in the log will contain 'cmdline: Pa
Well the reasoning is simple, It's tradition; a bootstrapper app has always
been a vehicle for delivery.
However, Burn does everything a traditional bootstrapper has always done (very
well) so us old guys feel warm & fuzzy - up to the point that the bundle
registers itself.
That said, after wr
On 05-Jul-13 11:57, Alain Forget wrote:
> I know the rule is that Components should always have unique GUIDs (at least,
> I think that's the rule).
Nope, it's way more complicated than that (as Rob's blog posts point
out). If it were that simple, MSI could generate the GUIDs for us or
eliminate
On 01-Jul-13 03:44, Kryschan wrote:
> We are really looking forward to a solution for this issue.
Then please file a bug with sufficient detail to reproduce the problem.
Obviously, WiX needs two different files to be able to diff them, so you
need to describe in more detail what you're doing that
On 04-Jul-13 16:28, Wesley Manning wrote:
> When I build my main bundle it copies over the addon EXEs to the
> release/debug folder but does not copy the MSIs of each addon.
WiX does that when building a bundle that has MSI packages with external
cabinets or files. Doing so for an uncompressed bu
I don't understand the reasoning here "I''m unwilling at this point to let
the bundle take over the handling of the MSI". What is the real difference
between having the Bundle registered as the ARP entry vs. the MSI
registered as the ARP entry?
Random note: Burn will clean up the package cache dur
I have tried but no errors of this kind.
> From: phil.wil...@mvps.org
> To: wix-users@lists.sourceforge.net
> Date: Fri, 5 Jul 2013 11:41:57 -0700
> Subject: Re: [WiX-users] Error 2705.Invalid table: Directory; Could not be
> linked as tree.
>
> Try the Orca ICE tests - ICE03 doesn't explicitly
The same file needs the same component guid because sharing is based on
component guids, so if two packages install the same file to the same
location Windows knows there are two products using the guid. If they have
different guids and you uninstall one of those products then Windows will
see the
Try the Orca ICE tests - ICE03 doesn't explicitly report that the directory
is not linked as a tree, but you may see something like:
ICE03 ERROR Not a valid foreign key; Table: Directory, Column:
Directory_Parent, Key(s):
Meaning that an entry does not have a parent in the Directory table.
P
I have an msi installer that compile fine but when I try to install, just when
it search for disk space it report error 2705, in the log there is something
like this:
MSI (c) (78:00) [08:43:29:440]: PROPERTY CHANGE: Adding ROOTDRIVE property. Its
value is 'C:\'.MSI (c) (78:00) [08:43:29:440]: No
I know the rule is that Components should always have unique GUIDs (at least, I
think that's the rule).
However, I have two packages that sometimes refer to and may install the same
files in the same location, so should the GUID be the same for both, so the
Windows Installer knows it's supposed
I think most of us use Properties like this:
NOT Installed AND NOT WIX_UPGRADE_DETECTED AND NOT
WIX_DOWNGRADE_DETECTED
WIX_UPGRADE_DETECTED AND NOT (REMOVE="ALL")
(REMOVE="ALL") AND UPGRADINGPRODUCTCODE
Installed AND (REMOVE="ALL") AND NOT (WIX_UPGRADE_DETE
I was faced with the same dilemma. I wanted to simply use the bundle to pave
the way for my main MSI.
As it is I've set the Permanent & Visible attribute of all the Package elements
in the bundle to "yes".
Thus when the bundle is finished it has an entry in the ARP but uninstalling it
essentiall
Hello all,
Need to find out if this is possible or if I've completely missed the point of
Bundles.
Is it possible to remove all traces of the bundle after installation, not just
hide it.
Essentially I want to use the bundle purely as a delivery method for the app
and its dependent apps (which
Hi I have my custom action defined like so:
NOT INSTALLED AND NOT UPGRADINGPRODUCTCODE
I only want the custom action to run on uninstall and not when getting
removed by an upgrade.
Is this possible?
Thanks Natalie
-
Look in the wix.chm file at the oage with HarvestFile target in the title where
those options are detailed for msbuild use.
> From: mark...@live.it
> To: wix-users@lists.sourceforge.net
> Date: Fri, 5 Jul 2013 00:29:52 +0200
> Subject: [WiX-users] Register dll for shell extension IThumbnailProvi
Look for all lines in the log referring to the MoveFiles action to see if your
file move operation shows up there or not.
> From: stephane...@hotmail.com
> To: wix-users@lists.sourceforge.net
> Date: Wed, 3 Jul 2013 23:37:08 -0600
> Subject: [WiX-users] WiX v3.7 - CopyFile not working
>
> I'm c
18 matches
Mail list logo
