[WiX-users] Custom Actions to manage a refcount (or something cleverer?)

I have several apps which need to set the same DWORD registry flag. The apps can be installed together (independently) on the same machine, so the flag must not be unset if one app is uninstalled while another is in place. Unfortunately the only permissible values for the flag are zero (or

Re: [WiX-users] avoiding GUID decoration in merge module property name

? E-Mail Me - Original Message From: Alan Sinclair alan.sincl...@citrix.com To: WiX-users@lists.sourceforge.net WiX-users@lists.sourceforge.net Sent: Mon, November 15, 2010 8:09:55 PM Subject: [WiX-users] avoiding GUID decoration in merge module property name I need to set a property

[WiX-users] avoiding GUID decoration in merge module property name

I need to set a property MYSPECIALDATA in a merge module, but the property name cannot have a guid appended because MYSPECIALDATA is read later by the consuming MSI (which doesn't know guids). Is there any way this can be done in WiX 3? I'd like to use a type 51 custom action to set the

[WiX-users] how can I check for FULL admin privileges

The MSI I'm working has an immediate custom action (after InstallFinalize) which writes to HKLM. On Win7 etc it fails even if the logged-on user is an admin unless it's run from an Admin Command Prompt (msiexec /i ...). How can I check for FULL admin privileges? Can it be done with Windows

[WiX-users] Odd ProcessComponents behavior in an upgrade

During an upgrade ProcessComponents is setting SharedDlls reference count to 2 instead of 1, for a component which has a file that was moved from a different component (seems like a bug in ProcessComponents, but who knows? it's consistent in Win2000 through Win7) Is there any good way I can

[WiX-users] illegal MsiFileHash entries

I'm using WiX 3.0.5419.0 to make a merge module, and my INF files (and only the INFs, no other files) are getting entries put in the MsiFileHash table. Candle and light are not complaining when they make the MSM, but when I use the merge module in an MSI, light correctly says light.exe :

Re: [WiX-users] conditional installation if application path found

what i'd do is 1 - have a property APPFOUND with a default value false 2 - use Appsearch to set the property to something (anything) different from false 3 - use a LaunchCondition that tests APPFOUND=false, with a suitable message shown when the test is true Condition Message=App is not

[WiX-users] Command line variables for Candle ? (Building both x86 and x64 in one makefile pass)

Can a WiX variable be passed into candle from the command line? Candle /? shows options but none seem to cover doing this. I need to compile both 32- and 64-bit merge modules from the same source, driven by the same makefile. Because of build complications (huge project) the makefile cannot

Re: [WiX-users] Command line variables for Candle ? (Building both x86 and x64 in one makefile pass)

oops -- how unobservant one can be !! candle /? says -dname[=value] define a parameter for the preprocessor -Original Message- From: Alan Sinclair [mailto:alan.sincl...@citrix.com] Sent: Friday, February 26, 2010 11:51 AM To: General discussion for Windows Installer XML

[WiX-users] table contains an action '' -- how to find it ??? (Light warning 1055)

Light is giving this warning: Console.wxs(142) : warning LGHT1055 : The table contains an action '' which cannot be merged from the merge module 'CDF.msm'. How can I find which action is colliding? Light omits the name, and there's no obvious culprit in CDF.msm (which is built elsewhere, and

[WiX-users] merge module schemata differences error halts nmake

I'm recoding a package in WiX. It includes a load of redistributable merge modules, and there are two different schemata defining the Feature and Feature_ columns. Light.exe gives this error: error LGHT0204 : ICE32: Possible Mis-Aligned Foreign Keys, Feature.1 = s38, Extension.Feature_ =

[WiX-users] dark.exe rejecting MsiAssembly table rows

Is there a problem with dark.exe (v 3.0.4805.0) in decompiling MsiAssembly tables? Dark is giving warnings like this: Migration.msm : warning DARK1059 : The MsiAssembly table contains a row with primary key(s) 'DataObjects.v0405.dll.5DF28CB2_8D5D_4385_994C_3AB91FB1B53A' whose Component_

Re: [WiX-users] how to change an installed package?

Thanks that will do it, provided that during the enumeration I can identify the original msi (which is created by our customers, as I'm just shipping a merge module.) I'd imagined using the handle of the currently-running msi (the newer version that's going to run RemoveExistingProducts) to

[WiX-users] mergemod CAs not getting into InstallExecuteSequence

I've got a merge module that's used successfully in dozens of packages. BUT ... in a new MSI the mergemod's custom actions are missing from the InstallExecuteSequence although they are getting into the CustomAction table. What might cause this? I'm building the package under VS2008 with WiX

[WiX-users] how to change an installed package?

This is not strictly a WiX question, but I'd *really* appreciate any suggestions! I shipped a merge module which customers build into their MSIs. The merge mod installs a device driver. The problem is that I did not properly allow for an upgrade. During an upgrade, the driver must NOT be

Re: [WiX-users] How to install a shortcut conditionally?

-Original Message- From: Bob Arnson Alan Sinclair wrote: I thought I'd make a new component (with condition on the component) and move the shortcut into that, but that was too simplistic and I don't know what KeyPath to use. I get ICE50 ERROR Component 'GuiDesktopIcon

[WiX-users] How to install a shortcut conditionally?

I've got a package (written in WiX 2) that installs three shortcuts. New request is for one shortcut to be conditional on a property. How do I make it work? I thought I'd make a new component (with condition on the component) and move the shortcut into that, but that was too simplistic and I

Re: [WiX-users] Interpreting Return Codes of Executable Custom Action (type 2)

My solution is to have the CA invoke a DLL, which in turn execs the .exe and interprets the return code. Yes, it's more work, but it works cleanly, and the DLL can hook into the MSI API to write to logs etc. -Original Message- From: DONG LEE [mailto:dongl...@gmail.com] Sent: Sunday,

[WiX-users] Why cannot use MsiNTProductType value in Condition?

MSDN says the way to recognize a server version of Windows is to use the MsiNTProductType property. Is there a reason why WiX 2.0.5805.0 will not let me use it in a LaunchCondition, like this? Condition Message=This application is not for Windows Servers VersionNT=500 AND

Re: [WiX-users] Why cannot use MsiNTProductType value in Condition?

? Alan Sinclair wrote: MSDN says the way to recognize a server version of Windows is to use the MsiNTProductType property. Is there a reason why WiX 2.0.5805.0 will not let me use it in a LaunchCondition, like this? Condition Message=This application is not for Windows Servers

[WiX-users] LockPermissions table not being created

I'm trying to set permissions on a directory, using this code: Component Id=MyDestFolder Guid={3E7974B0-F14A-4F9F-8CB1-D9737F658D51} DiskId=1 KeyPath=yes CreateFolder Directory=INSTALLDIR Permission User=NetworkService

Re: [WiX-users] LockPermissions table not being created

-users] LockPermissions table not being created If you use Extended=yes you're using SecureObjects instead of LockPermissions. Hopefully the verbose log file has information about what is getting configured. -Original Message- From: Alan Sinclair [mailto:alan.sincl...@citrix.com] Sent: Monday

Re: [WiX-users] Unresolved reference to symbol 'CustomAction:SchedSecureObjects'

Solved by including wixca.wixlib to light's input From: Alan Sinclair Sent: Wednesday, December 10, 2008 6:13 PM To: wix-users@lists.sourceforge.net Subject: Unresolved reference to symbol 'CustomAction:SchedSecureObjects' I'm trying to add code to set

[WiX-users] Unresolved reference to symbol 'CustomAction:SchedSecureObjects'

I'm trying to add code to set directory permissions, plagiarizing working code from another file. Adding the new code gets an error from light and it's got me baffled. Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder Name=PFiles Directory Id=MyStuff

[WiX-users] (no subject)

Can someone please tell me how to specify the data for a registry Type=multiString value? I've got a reg file entry like this [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MyDev\Parameters] IMOrder=hex(7):73,00,63,00,68,00,65,00,64,00,75,00,6c,00,65,00,72,00,0 0,00,\

Re: [WiX-users] (no subject)

/Registry From: Alan Sinclair Sent: Thursday, October 30, 2008 3:20 PM To: General discussion for Windows Installer XML toolset. Subject: Can someone please tell me how to specify the data for a registry Type=multiString value? I've got a reg file entry like

[WiX-users] Scheduling custom action at end of install

I need to have a merge module custom action happen at the end of the InstallExecuteSequence. Normally I sequence a MyFinalize custom action in a merge module as being after InstallFinalize, but if RemoveExistingProducts follows InstallFinalize then MyFinalize must be after

Re: [WiX-users] Where are binaries in MSIs from WiX?

Thanks! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: Wednesday, July 23, 2008 7:32 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Where are binaries in MSIs from WiX? Alan Sinclair wrote

Re: [WiX-users] Where are binaries in MSIs from WiX?

] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: Wednesday, July 23, 2008 7:32 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Where are binaries in MSIs from WiX? Alan Sinclair wrote: In the past I've found CAB files in the MSI's Binary table, and used

Re: [WiX-users] Where are binaries in MSIs from WiX?

In the past I've found CAB files in the MSI's Binary table, and used Orca to extract the CAB, then used Windows Explorer to get at the contents. But the MSIs produced by the WiX toolset on a project I've inherited don't have a CAB visible anywhere. The binaries are definitely inside the MSI,

[WiX-users] fragment compiles but is missing from MSI

I'm a WiX novice trying to add a new fragment to an existing mid-size package (currently compiled from 12+ fragments.) My new fragment is modeled on an existing working fragment. Candle and light both compile my new fragment but the resulting MSI doesn't include the file or CA from the fragment,

[WiX-users] LGHT0001 : Unknown error while getting hash of file

Any suggestions please as to what to look for to cure this error (in a WiX setup that I'm taking over from someone else)? We're using the final/stable WiX 2.0.5805. c:/PROGRA~1/WI577F~1/bin/light.exe -nologo -w0 -wx -pedantic:legendary -out Release/thecoapp.msi Release/oe.wixobj

Re: [WiX-users] LGHT0001 : Unknown error while getting hash of file

calculating the hash. Definitely could have a better error message (I *think* there is one in WiX v3). -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alan Sinclair Sent: Monday, May 12, 2008 19:05 To: wix-users@lists.sourceforge.net Subject: [WiX-users

Re: [WiX-users] wix mailing lists open to public = more spam

My vote is to require registration. It's really no big deal to sign up for a list, and I don't think it would make getting started significantly harder (newbie here, speaking from current painful experience -- probably signing up would give me a buzz of achievement that I'm not yet getting

[WiX-users] can wix 2.0 and wix 3.0 coexist?

newbie question: I've been playing with WiX 3 and Visual Studio 2008 (VS9) but now need to work on a project written for WiX 2.0 and VS 2005 (VS8). VS8 and VS9 coexist ok (so far) ... should I remove WiX 3 before using WiX 2, or can they also coexist (assuming paths are managed somehow)?

[WiX-users] good starting point for vs2008 votive wix?

Can anyone recommend a good place to start with Votive WiX on VS2008? I know a bit about MSIs from using Wise and Orca for some years, would like to maximize the Votive experience rather than hand-code WXS files. I've found a tutorial on CodeProject Creating an installer using Wix v3.0,

[WiX-users] beginning with Wix - which version?

If I'm moving to WiX, which version should I use. How far off is stable v3 likely to be? A colleague said "I would wait for a stable 3.0 before considering switching. Its vastly improved over version 2, and is not backwards compatible." Thanks