Re: [WiX-users] Trying to preserve installation location

Rob Mensching-4 wrote: > > Have you read the MSI SDK about major upgrades? It sounds like you're > not using the UpgradeCode to its full potential. > In what way?? I haven't read the MSI SDK docs - but I did read Phil Wilson's "Definitive Guide to Windows Installer" - Chapter 6, on Upgrades.

Re: [WiX-users] Proposal: Move WiX v3 to CLR 2.0

Rob Mensching-4 wrote: > > So, I'm wondering if anyone has an real objections to me moving the > minimum requirement to run the WiX toolset binaries from .NET Framework > 1.1 SP1 to .NET Framework 2.0. No objections whatsoever - I don't think .NET 1.1 is widely used anymore around here (Switz

Re: [WiX-users] Trying to preserve installation location

I found the problem: in order to get the "double-click the MSI to install" metaphor working, we're always creating a new ProductID with each build - the minor updates (leaving the ProductID intact and just updating the Version attribute) don't work, since double-clicking on such a MSI will only re

[WiX-users] Adding a to an existing component

Folks, I use WiX to build my MSI in an automated build environment. My challenge now is: I'm using TALLOW to create my directory listing, but after TALLOW runs, I should be able to add a tag to an existing component, in order to store the installation directory to the registry. I can't seem to

Re: [WiX-users] Trying to preserve installation location

Thanks for your response, Richard >>Are you setting the property before the user has a chance to specify >>the install location? You need to set the property after any changes >>to the install location are made. I'm trying to store the install location the user has picked into "ARPINSTALLLOCATI