Hi All!
Here is my xml:
...
...
...
...
...
1
...
...
On executing light.exe I got the following error:
error LGHT0094 : Unresolved reference to symbol
'CustomAction:[CustomSerialValidateProp]' in section
'Product:{3E8964C7-5FA5-4740-A3D6-191E2043963C}'
According to
http
Thank you, it works!
Only two questions: First, is it possible to retain checkbox state when
user is launching the installer when application is already installed and
the user chooses Change?
Second is that, now I am getting two warnings on build of installer:
ICE30: The target file 'rqpg5ev7.con|W
Many thanks for that; I added the various flavours of the
prerequisites to my package (when you have 25+ dependencies already in
your source tree, what's four more?!), and now it builds nicely.
On 8 December 2011 01:07, John Cooper wrote:
> In answer to the first question, I believe you currently
How do I force Windows Install to restart Explorer after it kills it?
> -Original Message-
> From: Bob Arnson [mailto:b...@joyofsetup.com]
> Sent: Monday, October 17, 2011 8:39 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Uninstall stops Explorer but doesn't restart
So I've been running in circles trying to build burn, and always end up
with the following error:
[readregistry] Registry Path Not Found! -
key='Software\Microsoft\VisualStudio\VSIP\10.0\';hive='LocalMachine';
The only other person experiencing this problem with 3.6 ended up not
building at all,
Turns out my problem was that the key was being created, but under the
HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall key so I
didn't see where it went.
The installer was built and installed on Windows 7 64 bit, but I hadn't set the
Platform='x64' value in my section. On
Create 2 components, 1 component for each text file. Give them * guids. Use
the same element's Name attribute in both components but point the
Source attributes at different versions of the text file in each
component. Add a condition to each component: one component's condition
should be true if
Hello all,
I got a task of modifying an existing WiX installer. The files are
copied in batches (File elements inside DirectoryRef elements) and one
of these files (let's name it file.txt) should be modified if a checkbox
was checked in one of the installer screens. I was able to create the
che
Thanks. I did exactly that and the ARP* properties are working just fine.
I love this thing ;-)
On Wed, Dec 7, 2011 at 10:00 AM, Tobias S wrote:
> Personally I tend to set AddRemovePrograms="no" to prevent drivers
> from showing up in ARP. Mean otherwise the user could uninstall the
> drivers w
http://msdn.microsoft.com/en-us/library/windows/desktop/aa368032%28v=vs.85%29
.aspx
-Original Message-
From: wigyxz-p...@yahoo.com [mailto:wigyxz-p...@yahoo.com]
Sent: 07 December 2011 16:57
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Creating HKLM\Microsoft\Windows\CurrentV
I would like for my wix-generated install to create the various registry
entries under HKLM\Microsoft\Windows\CurrentVersion\Uninstall\{Product-code}
MSDN seems to indicate that these keys are updated by the Windows Installer
service (see link below), but my installs created with Wix don't seem
I made up a test installer that has the Welcome Dlg, License Dlg, a simple
custom dialog and then the rest of the standard dialogs.
I install it and then run the install again to uninstall .. from the same
command window (cmd.ex), I still get the same scenario ...
1. MaintenanceWelcomeD
Personally I tend to set AddRemovePrograms="no" to prevent drivers
from showing up in ARP. Mean otherwise the user could uninstall the
drivers while leaving back the application which IMHO makes no sense.
Back to your question AFAIK configuring the ARP entries is done inside
the DifX driver.
Rega
In answer to the first question, I believe you currently need it when you build
the bootstrapper as it extracts some info from the package. For the second, I
believe it will work, but I have no experience with that. As to the third, I
believe they're the same except that the ARP properties pro
The MSI team recommend that you create separate MSIs for per-user and
per-machine because they are hard to create correctly. If you are using only
MSI v5, there is better support for dual-purpose packages.
http://msdn.microsoft.com/en-us/library/dd408068%28VS.85%29.aspx
The log entry tells you tha
15 matches
Mail list logo
