do is have the
installer create shared files as well as the installed product and make one of
these an .inf file that contains the installed information that your support
desk can check to see if the product was EVER installed.
Richard Horsley
-Original Message-
From: Markus Karg
indows Installer XML toolset.
Subject: Re: [WiX-users] Prevent deinstallation
In theorey we could, but:
Will this solve the problem?
Will the user be able to see that the module was installed?
> -Original Message-
> From: Richard Horsley [mailto:richard.hors...@eicltd.com]
> Sent: Do
Could you create an .msp to patch the original installer to add these files?
-Original Message-
From: Markus Karg [mailto:k...@quipsy.de]
Sent: 01 April 2010 10:30
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Prevent deinstallation
We have to write a .msi
-out imp.wxs -template:product -scom -sreg -sfrag
-gg -suid
From: Richard Horsley [mailto:richard.hors...@eicltd.com]
Sent: Wed 3/31/2010 1:46 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Heat harvesting and fragment/component generation.
Previousl
y at a later date (and
for patching purposes). I'm sure other people have done this before (and I
believe that WiX 2.0 actually used to harvest files in this way), anyone got
any ideas?
Richard Horsley
-Original Message-----
From: Richard Horsley [mailto:richard.hors...@eicltd.com]
Sent:
there any way to get heat to place all files from the same subfolder within the
same fragment/component, or is this not considered best practice?
Richard Horsley
DISCLAIMER
Please consider the environment before
Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Richard Horsley [mailto:richard.hors...@eicltd.com]
Sent: 25 March 2010 12:23
To: General discussion for Windows Installer XML tools
As I said a bit further back, installing regular x86 MSI's on x64 windows
systems works absolutely fine. It will automatically use SysWOW64 instead of
system32, Wow6432Node for registry settings and Program Files (x86) for the
actual program directory. Unless you specify otherwise, this is the d
f Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Richard Horsley [mailto:richard.hors...@eicltd.com]
Sent: 25 March 2010 11:14
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] MSI patching for two versions of the same MSI?
When I have done this before, the msiexec on the machine installing the
software has always handled the package correctly (placing items in syswow on
x64 machines for files and registry as well as Program Files (x86)) on both
machines. AFAIK you only need to specify x64 folders if your package
iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP Email Disclaimer
-Original Message-
From: Richard Horsley [mailto:richard.h
tor
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Or
I have a WIX patch that I need to apply to all client PC's with a particular
product installed. I generated the original MSI and have the WIX script that
was used to create it. The process has gone like this:
MSI installer v1.0 created and distributed to 50% (ish) of client machines.
MSI install
13 matches
Mail list logo
