What does the verbose log file for the last install say? It should explain
why it chose not to install that Component.
Have you considered moving to WiX v3.5 and getting rid of Component/@Guid
completely and letting the WiX toolset manage the GUIDs for you?
On Fri, Dec 3, 2010 at 3:52 AM, Ilya Sl
No, nothing in the Windows Installer supports that sort of scenario. Not
exactly sure what that would accomplish anyway. How would you patch or
update such files? Presumably you'd have to list them with the Windows
Installer somehow and that would get you right back where you are.
Now, it would be
Fredrik is working on Burn. Therefore, it rocks!
On Fri, Dec 3, 2010 at 10:06 AM, James Johnston wrote:
> Probably, except that there were some reasons why I decided against
> dotNetInstaller. In the end, given that I had only one prereq (DOTNETFX
> 2.0), I used the VS2008 bootstrapper because
Yes, fixed in v3.5 in the last month or two (Office found it and fixed it,
IIRC).
On Fri, Dec 3, 2010 at 6:57 AM, Yaroslav Lobachevski wrote:
> Hi,
> our building system uses symbolic links heavily. The links are fed to wix
> instead of real files. Correct binaries are included in a installer, bu
Burn has no dependency on the .NET Framework. I wrote the
BootstrapperApplication for the WiX toolset in managed code to verify that
it was possible. The WixStandardBootstrapperApplication is all native.
Yes, Burn can do exactly what you are talking about. You can list both
Packages and set the In
Mark the CustomAction/@HiddenTarget="yes".
On Thu, Dec 2, 2010 at 2:54 PM, Gocek, Gary wrote:
> We're using the WIX 3.0 setup.exe bootstrapper stub as our bootstrapper
> stub, even though we're otherwise using WIX 3.5. This is because the stub
> was removed from WIX 3.5 (I don't know why). And b
Yes. Actually, it's required. The Chain defines the Package order. You can
also Fragment your PackageGroups and tie the chain back together using the
After attribute.
On Thu, Dec 2, 2010 at 6:49 AM, Simon Chromow wrote:
> Hello,
>
>
>
> I'm using WIX 3.6.
>
> Is it possible to define the order, h
Like you, I've been playing around with Burn. Here's what I got to work in
the 3.6-1125 build:
---
http://schemas.microsoft.com/wix/2006/wi";>
---
This builds a setup.exe with its own GUI
Hi All,
Our software has to install a large number(more than 50,000) of files at
target machine and We followed one component per file strategy(as
recommended by WIX and MSI). While doing major upgrades it consumes a
lot of time(sometimes 30 minutes) on some of the screens.
I want to compress
Probably, except that there were some reasons why I decided against
dotNetInstaller. In the end, given that I had only one prereq (DOTNETFX
2.0), I used the VS2008 bootstrapper because it's supported by Microsoft;
seems to work well at what it does. Also works with MSBuild. If I replace
this wit
Wouldn't it be simpler to have 1 executable that does all the work for
you rather than this chain of executables ending in MSI's?
dotnetinstaller (http://dotnetinstaller.codeplex.com/) for example could
simplify that whole convoluted process to 1 executable containing both
your MSI's & all your ca
Right; it comes in a self-extracting EXE that then launching the VS2008
bootstrapper. The generated VS2008 bootstrapper EXEs have the MSI name
embedded in them so there are two VS2008 bootstrapper EXEs: one for each
MSI. I wrote a custom program in C that the self-extracting EXE launches.
This ap
Hi,
our building system uses symbolic links heavily. The links are fed to wix
instead of real files. Correct binaries are included in a installer, but
zero is written in FileSize column of File table.
Is it a wix bug?
How critical is the field value? I believe file space needed for
installation is
Blair,
We do not have shared components, shared GUIDs are used only for
installer development efficiency. In some installers we have up to 15
products (with different ProductCode and PackageCode) that are built
from the same source files. 15 sets of GUIDs are not as convenient as a
single set.
Be
It seems wrong to me, but perhaps there is no real harm done having the key
paths
in HKCU, when the shortcuts are in the machine context?
2010/12/2 Pally Sandher
> That's what the WiX documentation recommends ->
> http://wix.sourceforge.net/manual-wix3/create_start_menu_shortcut.htm
>
> Palbind
Thanks you Blair, for quick response!
Igor
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Thursday, December 02, 2010 2:19 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Bootstrapper and Repair
As far as I know, there is no way to g
I managed to solve the problem. Even none of the components install any
files it is still important they "install" to the same folder. So the trick
is to replace the directory tree with this one:
Nevertheless, I appreciate any feedback more experienced users can give me
on this soluti
Hi,
Am just playing a bit with burn from the newest build. My goal is just
to have a working setup.exe package containing a msi to be installed.
Can anybody post me a workign simple sample for that use case or give
me a hint based on my below described solution? Based on the actual
help and the in
Hi,
In theory (productive usage not yet) I did some similar for an
installer. The huge asset is e.g. for a wow64 application only
containing device drivers for x86 and x64 the saving e.g. for a CD
shipping both versions is enormous here. When a bundling technique is
used the customers can download
Hey,
Thanks for your answers. I will just post the WiX Code of the merge module.
Maybe that can cast some light on this:
http://schemas.microsoft.com/wix/2006/wi";
xmlns:iis="http://schemas.microsoft.com/wix/IIsExtension";
xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";>
20 matches
Mail list logo
