Also note the WiX toolset preserves the timestamps on the files in the
cabinets. If you want control over the times of the files, set them before
creating the MSI.
On Tue, Sep 27, 2011 at 9:35 AM, Wilson, Phil wrote:
> Windows Installer will set the Modify and Creation dates of data files to
> be
AFAIK, merge modules aren't treated differently from MSIs wrt * GUID.
On Tue, Sep 27, 2011 at 6:22 AM, Christopher Painter wrote:
>
>
> Rob,
>
>
> Has WiX implemented "*" for Merge Modules yet? I understand Merge
> Modules are retargetable but then again any MSI is really retargetable by
> cha
On 27-Sep-11 19:23, Albert Attia wrote:
> The property is named plural for multiple paths (which light.exe supports by
> multiple -b arguments), however how do we specify multiple paths on the
> property?
>
> I have tried separating the paths with ";" and ",", both do not work.
How does it not work
On 26-Sep-11 13:18, John Bergman wrote:
> That's right.
>
> We use the workflow based logic to perform additional functionality, such as
> bundling files into zip files, backing up databases and running automation.
> (not to mentioning deploying and running the automated builds in the lab
> env
The PropertyGroup MSBUILD Task on WIX lets you set the LinkerBaseInputPaths
property, its essentially the -b parameter for light.exe.
The property is named plural for multiple paths (which light.exe supports by
multiple -b arguments), however how do we specify multiple paths on the
property?
I ha
Corner Geoff wrote:
>
> The way to go with WiX seems to be to create an overall wxs file and
> have a sub file for each component,
>
In the tutorial, it says: "In general, you should restrict yourself to a
single file per component"
What this means is that you (in general) should only have o
Windows Installer will set the Modify and Creation dates of data files to be
identical when they're installed - is that what you're seeing? That's to
identify modified-after-installation files. Maybe sometimes that's a "future"
date.
Phil Wilson
-Original Message-
From: Christopher P
Rob,
That was a most thorough answer, thank you very much.
My questions (regarding THIS subject) has been fully answered.
Med venlig hilsen / Best regards
Thomas Due
Software udvikler
Scanvaegt Nordic A/S
Fra: Rob Mensching [r...@robmensching.com]
Sendt
Rob,
Has WiX implemented "*" for Merge Modules yet? I understand Merge
Modules are retargetable but then again any MSI is really retargetable by
changing the value of TARGETDIR/INSTALLDIR/INSTALLLOCATION et al. That of
course has always struck me as odd about the whole MSI Component ID
Well, my opinion is my opinion. People are welcome to disagree with my
opinion
For example, a few people around here (including some clients) disagree with
me whether MajorUpgrade/@AllowSameVersionUpgrades is a "good thing" or not.
It's only when something *really* doesn't work and people want t
InstallShield doesn't "hide" any of the details. It's all right there in
the Direct Editor if you choose to look at it. (Which you should.)
WiX has some advatanges and disadvantages as compared to InstallShield but
at the end of the day it's the skill and the dedication to quality of the
setu
WiX / MSI doesn't have any elements/table data to express file timestamps.
This is a function of when the file is compressed into the CAB.
I don't see anything strange about the behavior as it's expected since
windows is aware of UTC and Local time and will use UTC internally but show
Local
I think it unlikely that the tutorial recommends a file per component. I
think you misunderstood that part: it would be excessive. For 30-40
components, I'd just use a single file and not worry about fragments.
Fragments are useful for sharing sections of code between installers or
wixlibs and for
Hi,
I am here in search of relief from the InstallShield "treacle machine".
WiX looks like an answer to my heartache of trying to maintain an
Installation project I inherited a few years ago.
I have read the tutorial and the first few bits of the Manual - I have
installed WiX 3.5 and use Vi
Hi all,
I have noticed a strange behavior during installation.
For example, we have a build server with UTC+01.00.
I have a production server with UTC-06.00.
I run a build on the build server and create an installation.
I install the installation on the production server and can see, that "modify
15 matches
Mail list logo
