Using MsiSetTargetPath(hInstall, INSTALLDIR, szLocalPath); has worked
perfectly.
Thanks Peter
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 27 July 2012 16:12
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Custom
I've got an installer with a couple features, and they can either all be
installed on one machine or on multiple machines. The features write values
to the registry to auto-populate properties on upgrades, however some of
the features use the same properties (database location, for example). What
I am trying to suppress the reboot after installing .NET Framework 4.0.
Its log shows that it is returning 3010. I have coded the .NET
Framework 4.0 as an ExePackage and have coded an ExitCode with
Behavior=success for the 3010, yet the bundle wants to reboot after
installing .NET Framework 4.0.
You could try
ExitCode Value=3010 Behavior=scheduleReboot /
instead of having it as success but there is a built-in packagegroup for
.net 4 anyway. See the help for wixnetfxextension.
PackageGroupRef Id=NetFx40Redist /
-Original Message-
From: Ross M. Del Busso
Defect raised: 3552167
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: 29 July 2012 20:34
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Stdba HyperlinkTheme
On 27-Jul-12 12:38, Neil Sleightholm wrote:
That sort of works; if I add the image to the
Thanks to Bob for pointing out that the VC10 merge module no longer installs to
the winsxs directory. Now it installs to Windows\System32.
My question then is how can I using Wix set the merge entry to *not* try to
install the VC10 merge module if it already exists on the system? The problem
Hello
I have a web.config which the following entries in the runtime tag:
configuration
.
runtime
assemblyBinding
dependentAssembly
assemblyIdentity name=Assemblyname1
publicKeyToken=somevalue/
That will be the default behavior. Look at the verbose log file to see why
the Windows Installer thinks it needs to install the files.
On Mon, Jul 30, 2012 at 3:59 PM, Chris Dahl chris.d...@nitropdf.com wrote:
Thanks to Bob for pointing out that the VC10 merge module no longer
installs to the
Hello
I have a web.config which the following entries in the runtime tag:
configuration
.
runtime
assemblyBinding
dependentAssembly
assemblyIdentity name=Assemblyname1
publicKeyToken=somevalue/
On 30-Jul-12 18:59, Chris Dahl wrote:
My question then is how can I using Wix set the merge entry to *not* try to
install the VC10 merge module if it already exists on the system?
1. Worth noting: Merge modules are a build-time concept; once merged,
they lose their identity as a
10 matches
Mail list logo