[WiX-users] WiX Install path

I have just updated to WiX v 3.0.4603.0 and the install location has changed, it was "C:\Program Files\Windows Installer XML Toolset v3" and it now "C:\Program Files\Windows Installer XML Toolset 3.0.4603.0". This seems to have broken Visual Studio projects which are still looking in "C:\Program Fi

Re: [WiX-users] WiX Install path

I believe you can just change the value of the $(WIX) environment variable to point to the right place (at least this is the case with 2.0) Neil Sleightholm wrote: > I have just updated to WiX v 3.0.4603.0 and the install location has > changed, it was "C:\Program Files\Windows Installer XML Tool

Re: [WiX-users] WiX Install path

I don't know whether the change was intentional, but to fix this you can edit the .wixproj file to redirect the location. See the "Using WiX with MSBuild" topic in the WiX.CHM for the property you need to set. Neil From: Neil Sleightholm [EMAIL PROTECTED] Sent:

Re: [WiX-users] Dependencies and merge modules

[EMAIL PROTECTED] wrote: > Is there good documentation on how to detect application dependencies Your dependencies should be explicit: Taking a dependency on a particular component means keeping track of it, preparing for updates, and so on. > and locate suitable merge modules? > Always ge

Re: [WiX-users] Problem using FirewallException

Paul Lalonde wrote: > I removed the Assembly and AssemblyApplication attributes as you > suggested. The installer was already running with full UI. This is on > x86. > > Unfortunately, the results were the same: abrupt rollback, no error > message to the user, and nothing in the log. > I

Re: [WiX-users] Re 4: Patching and sqlscript element (to Bob Arnson)

Victor V. Sergeev wrote: > Also I try change size of sqlscript element source from 300 bytes to > 3 bytes, but size of .msp file not change. > That means the data didn't get filtered into the patch. If you're using explicit filtering, you'll need to use BinaryRef to pull it in. -- sig:/

Re: [WiX-users] Features in different .msi

Alex Ivanoff wrote: > Yes, you are right: I want the same product codes. Here is some > scenarios. > > a1.msi has feature A1 of product A, a2.msi has feature A2 of product A. > You can use one .msi with multiple Features. -- sig://boB http://joyofsetup.com/

Re: [WiX-users] Component condition ignored during Upgrade

PameAlex wrote: > Another thing kind of curious is the fact that the other > property(OLDAPPFOUND) I am using to avoid the component to be installed > during the Upgrade is working so the issue is only in the uninstallation > part. > You're not going to be able to use component conditions to pr

Re: [WiX-users] How to create shortcut to an existing application?

Andrew Kendall wrote: > The product I am installing is a plug-in for another application, and I want > to create a shortcut for the 'mother' application already installed on the > users machine. All the examples I have seen so far declare Shortcut elements > as children of File elements, but tha

Re: [WiX-users] WiX Install path

Neil Sleightholm wrote: > I have just updated to WiX v 3.0.4603.0 and the install location has > changed, it was "C:\Program Files\Windows Installer XML Toolset v3" and > it now "C:\Program Files\Windows Installer XML Toolset 3.0.4603.0". This > seems to have broken Visual Studio projects which are

Re: [WiX-users] Heat.exe and '1 directory - 1 component' mode

Yan Sklyarenko wrote: > Does heat.exe utility support the mode "1 directory - 1 component", when > it harvests all the files of a certain directory to a single component? > No. Harvesting one file per component helps prevent component-rule violations. -- sig://boB http://joyofsetup.com/ -

Re: [WiX-users] Features in different .msi

I know, but it was not my question. -Original Message- From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Saturday, October 11, 2008 15:24 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Features in different .msi Alex Ivanoff wrote: > Yes, you are right