I've been playing with understanding upgrading in MSI/WiX, but the thing that
I've not yet understood is that the upgrade appears to happen completely
silently.
How do I get some kind of feedback in the user interface to say "we've found
version x already installed, this will upgrade it", and ma
Hello,
I am trying to create a shortcut from the Desktop to a virtual location in
"Computer" or "My Computer" .
This is easily done in Windows by dragging the virtual folder (MyFolder)
from the Tree View in Explorer up to Favorites in Windows 7, but I cannot
replicate this using WiX.
Target Typ
I found the answer here (from Bob Arnson):
http://stackoverflow.com/questions/7588259/wix-specify-the-installlocation-of-packages-inside-the-burn-managed-bootstrapper
"Use an MsiProperty child for each MsiPackage to specify
INSTALLLOCATION=[BurnVariable]. Then use Engine.StringVariables to set
Bu
Bob Arnson wrote:
>
> It does by default. Look at verbose build output to make sure -sval
> isn't being passed.
>
I checked and I'm not suppressing any ICE validation. I tried again in Orca
and realized I was running the full test suite and not just the Merge Module
validations. It tried aga
Hi...
Our installers are used internally to install to a farm, so we
had
In our old Wix 2.0 scripts. We recently updated to Wix 3.5, and I started
getting ICE48 warnings. I googled around on how to do this "properly", and I
found some posts about moving the definition of th
Nope, FILETIME is not timezone aware...
Want to hear something even stranger? When you ask for a FILETIME to be
resolved, it uses the "is daylight savings time?" setting from *now*, not the
date on the file to adjust the timestamp.
Want to hear something even stranger than that? The C runti
I did some googling but had decided not to post since I'm not an expert. I
found some doco in MSDN describing a structure with Date and Time fields
and a note saying that it's generally date modified but that the meaning is
up to the application. Nothing in the datatype seemed to be UTC aware.
I believe this is a limitation of .cab files that store the times as
FILETIME. Timezone is not stored. I'd be happy to be wrong if someone could
show otherwise.
On Wed, Sep 28, 2011 at 4:53 AM, Grigory Konovalov <
grigory.konova...@confirmit.com> wrote:
> Why WIX save local time for files, but do
I have notice on Nabble that their are several posts which do not specify a
sub-forum (the options are wix-user or wix-devs) which corresponds to the
two different mailing lists.
I am not sure, but I believe that if you don't choose a sub-forum then your
post will only be seen by those who actuall
I understand how the GUIDs are generated. My question goes deeper and
hits at the annoyances of needing components and GUIDs in general but I'll
leave that for a blog post some day.
From: "Peter Shirtcliffe"
Sent: Wednesday, September 28, 2011 6:52 A
Why WIX save local time for files, but doesn't save UTC time?
For example, a file has 10.00 time modified in a server with UTC+01.00 (it is
9.00 in UTC time).
I create msi on this server and install it on a new server with UTC-01.00.
The file have 10.00 time modified on the new server after instal
This may clear up your confusion.
The * guid is generated based on the path in the installer at build time, not
based on the path with the substitutions made at install time.
For example:
A component's path at build time is [ProgramFilesFolder]\Company\INSTALLDIR
A component's path at install tim
You have to implement ComponentGuidGenerationSeed to use "*" in a merge
module and you wouldn't if you used a fragment instead. I wonder if WiX
could be changed to just use the Module Id for it's GUID by default?
My point still stands though as an MSI can have it's INSTALLDIR changed so
the
13 matches
Mail list logo
