[WiX-users] WiXUI errors

I'm using command line: c:\work\installlight setup.wixobj -ext WixUIExtension and i'm getting such an output: Microsoft (R) Windows Installer Xml Linker version 3.5.1030.0 Copyright (C) Microsoft Corporation. All rights reserved. c:\work\install\setup.wxs(1571) : error LGHT0094 :

[WiX-users] _Validation table

Hello, Could you please explain what's the purpose of the _Validation table in MSI files? How is the long Description column used? How much overhead does this table add to my MSI and how can I reduce it? Thank you, Piotr

[WiX-users] wix upgrade issue.

we have upgrade all the visual studio projects to visual studio 2008 But In Build machine we have visual studio 2005 and Wix 3.0.5419(Wix is upgrade from Wix3.0.2925). I have not upgraded Visual studio 2008 in build server. I installed .NET Framework3.5 and compiling all the .net projects. we

Re: [WiX-users] Component Keypath Problem

ricky sundrani wrote: I have a component whose purpose is to modify the machine.config file. What it does is add a new line to machine.config using XmlConfig element. But when i clicked on the repair button for repair, the component described above is called again i.e the line which was added

Re: [WiX-users] Problem with WiX/MSBuild with TargetPath

Fenstad, Darrel B wrote: I have read the closed Tracker Item https://sourceforge.net/tracker/index.php?func=detailaid=2777114group_id=105970atid=642714. It and another page I found on the Web implies that a fix went into WiX 3.0.5322.0 to address this issue. However, I am using WiX

Re: [WiX-users] Bug causing ICE 17 failure

Rob Mensching wrote: It has been a long time since we found a dependency between tables that wasn't automatically added by the WiX toolset. Is it possible that a ControlCondition table is required by the ICEs whenever there is a Dialog table... or something screwy like that? Apparently,

[WiX-users] Remove registry entry on install

I need to prevent users from uninstalling my app via the Add/Remove Programs Tool. To do that I need to remove a registry entry (http://support.microsoft.com/kb/314481). I've tried using the following Wix code, but it has no effect: Registry Id=UninstallKey Root=HKLM

Re: [WiX-users] Component Keypath Problem

Hi Bob, I set the REINSTALLMODE property to 'p' and its working fine now as per my requirements. Thanks. On Tue, Dec 1, 2009 at 5:59 PM, Bob Arnson b...@joyofsetup.com wrote: ricky sundrani wrote: I have a component whose purpose is to modify the machine.config file. What it does is add

[WiX-users] error message for 64 bit installer on 32 bit machine

Hi, When we try to install a 64 bit MSI on a 32 bit machine, the error message is not clear. The error message is: This installation package is not support by this processor type. Can we change this message? Thanks Regards, Srivardhan.

Re: [WiX-users] _Validation table

Besides what is available on MSDN (e.g. http://msdn.microsoft.com/library/aa372930.aspx) what more do you need to know? -Original Message- From: Piotr Fusik [mailto:pi...@fusik.info] Sent: Tuesday, December 01, 2009 2:39 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users]

Re: [WiX-users] WiXUI errors

I don't recognize the SUFWI dialog set and WixUIExtension doesn't either. The only UI types in WixUIExtension are WixUI_Advanced, WixUI_FeatureTree, WixUI_InstallDir, WixUI_Minimal, WixUI_Mondo. -Original Message- From: pushist1y [mailto:mister.p...@gmail.com] Sent: Tuesday, December

Re: [WiX-users] website being removed after upgrade

As a general rule, if the component is simply an upgraded version of its previous self and could assume the same identity, it's guid should stay the same. So, no, don't change the guids. One possibility would be to create an HKLM registry value as the keypath of the IIS components (a different

[WiX-users] setupbld diagnosing?

My WiX project has a handful of prerequisites, for example, the application requires .NET 3.5 SP1. My WiX project correctly does not run unless SP1 is installed. I understand that this needs to be done in a bootstrapper. However, after a couple of hours of reading on the Internet and

Re: [WiX-users] Pyro error

If the warning is not causing any issues I think we can ignore that. We can take care of this in the SP1 release. No I did not. DO you want me to try it with the option? Ok let me know if you need any information. Thanks Anurag -Original Message- From: Blair [mailto:os...@live.com]

Re: [WiX-users] setupbld diagnosing?

John L Krupka wrote: You should be able to set up preconditions on those things in the msi. Setupbld is not the place for that to the best of my knowledge. This is where my lack of understanding how MSIs work raises its head. My MSI has a condition where it needs .NET 3.5 SP1, and