Re: [WiX-users] Is it safe to use a CustomAction longer than 255 bytes?

Dominic Herity wrote: > What are the consequences of an excessively long command line? > A truncated command line could be dealt with, but if the result is "undefined > behaviour" and a destabilised msi, that's another matter. > It is undefined. But probably works. -- sig://boB http://joyofs

Re: [WiX-users] Getting Started

richard develyn wrote: > It may be better for me simply to start again. Where should I get the latest > WiX version from (for VS 2008 and Vista) and what do I need to install for > what I need to do? > The latest WiX release is always available at http://wix.sourceforge.net/releases/. -- sig

Re: [WiX-users] Radio button group with all buttons unchecked by default in WIX3

Alexey Doctorovich wrote: > I want to implement a radio button group, so that initially all buttons are > unchecked. MSI doesn't support that (though it obviously works). That's what the ICE34 message says. -- sig://boB http://joyofsetup.com/ ---

Re: [WiX-users] Feature Conditions Not Being Applied

jnewton wrote: > I have several features in my installer feature tree. Some have conditions > based upon App and Component searches. See http://www.joyofsetup.com/2007/05/30/feature-conditions-and-ui/. -- sig://boB http://joyofsetup.com/ ---

Re: [WiX-users] Looping through registry keys

lesterbangs wrote: > The no-brainer pattern for this type of search is obviously a loop, but I > don't think this can be translated into a WiX equivalent. The problem is > that there may be a variable number of subkeys that may be present, and any > one of them could contain the needed value. So

Re: [WiX-users] Getting ICE20 errors (not found in 'InstallUI/AdminUISequence" Sequence Table

David Bartmess wrote: > I'm getting the following errors from the code below. How can I get rid of > these errors? > You have to follow all the requirements of a UI if you're doing your own. See ICE20 in the SDK for details. -- sig://boB http://joyofsetup.com/ ---

Re: [WiX-users] cabinet file can not be found if the file path contains double byte characters

azurejyl wrote: > I've made the product code page to "65001", which supports UTF-8, MSI doesn't officially support Unicode. -- sig://boB http://joyofsetup.com/ -- Apps built with the Adobe(R) Flex(R) framework and Fl

Re: [WiX-users] Custom dialog during uninstallation

Jan Bilek wrote: > My problem is simple: I need to ask user before an uninstallation > begins, whether he wants to keep or remove user created files (settings, > database, etc.). > There's no way to force a user to answer that question. The closest you can get is to set ARPNOREMOVE to force

[WiX-users] Feature Conditions Not Being Applied

I have several features in my installer feature tree. Some have conditions based upon App and Component searches. I see that the properties of the conditions are being set, but it doesn't seem like my Features are turning on and off based on them. My Features are always turned on. I even set the

Re: [WiX-users] Upgrading ...Not happening

Are you changing Product/@Id on each build? There is an example of a major upgrade script here: http://neilsleightholm.blogspot.com/2009/01/wix-script-for-major-upgrade s.html Neil -Original Message- From: Hukumchand Shah [mailto:hukum.s...@gmail.com] Sent: 21 March 2009 07:27 To: Gener

[WiX-users] Upgrading ...Not happening

Hi All, I want to do upgrade in my current WIX installer. I am changing the Version shown below. and also adding the upgrade element: But when I make .msi and run it by double clicking then it shows error meaasge attached with mail. I also checked the log files, it