[WiX-users] Candle: Add new GUIDs to user specified locations at compile time?

Hi Is there a way that a new GUID can be added to specific location within WiX at compile time? I have created a common WiX file, and I want to add a new GUID upon each run to: * Product Id * Product UpgradeCode * Component Guid I read in one blob http://johnmcfadyen.spaces.live.com/?_c11_Blog

Re: [WiX-users] Program Menu: Target shortcut is a Directory

Thanks for the reply I looked in the http://www.tramontana.co.hu/wix/index.php WiX Tutorials , but I did not find any information on [%ComSpec] What is it? - Thanks Jeff in Seattle -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Program-Menu

Re: [WiX-users] heat.exe: Harvest contents of directory and NOT the directory name

I took some hunting but I found the flag (have not tried it yet) http://www.tramontana.co.hu/wix/lesson6.php http://www.tramontana.co.hu/wix/lesson6.php Yet another switch, -srd will suppress the identifier generation for the root folder specified. File components in the root folder will refer

Re: [WiX-users] heat.exe: Harvest contents of directory and NOT the directory name

Thanks for the reply, However, I do not see suppress root directory flag viewing the following heat.exe documentation link: http://wix.sourceforge.net/manual-wix3/heat.htm http://wix.sourceforge.net/manual-wix3/heat.htm - Thanks Jeff in Seattle -- View this message in context: http://win

[WiX-users] heat.exe: Harvest contents of directory and NOT the directory name

Hi I have a directory .\foo\ that has contents I want to harvest. However, in the end, my INSTALLDIR within Harvester.wxs contains directory foo and then its components, and I want only want is components. In other words, my current harvest is this... But I wan

Re: [WiX-users] Program Menu: Target shortcut is a Directory

Addendum: I have actually defined as follows: - Thanks Jeff in Seattle -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Program-Menu-Target-shortcut-is-a-Directory-tp4966880p4971822.html Sent from the wix-users mailing list archive a

Re: [WiX-users] Program Menu: Target shortcut is a Directory

Thanks for the reply, Using the WiX schema you had provided, will need a Name: And using a shortcut name of "MyShortcutName" The program menu will be: All Programs >> MyProduct >> MyShortcutName Instead of what I am trying to g

Re: [WiX-users] Program Menu: Target shortcut is a Directory

Thanks for the reply I am getting close, but I am getting a cascading program menu item. I trying to setup Platform Tools as my folder shortcut. This is my current status All Programs > Platform Tools > Platform Tools I tried, but no program menu item app

Re: [WiX-users] Windows 7 x64: Windows application x64 is looking for MSVCR71.dll

Thanks for the reply, I do not have control of the build; in other words, I am provided with an x64 build and I do not have the sources. This x64 binary is from the open source community. Thereby I must merge msvcr71.dll with install upon a Windows 7 x64, or a getting "missing" error dialog at r

[WiX-users] Windows 7 x64: Windows application x64 is looking for MSVCR71.dll

Hi I am building a WiX x64 install and I want to merge into the install an MSM (Microsoft Merge Module) for an Windows x64 application that is needing MSVCR71.dll. The deployment of this application is intended for Windows 7 x64. Which merge module should I be using? I thought maybe I should be

[WiX-users] Program Menu: Target shortcut is a Directory

Hi I am creating a set of SDKs. I want the Shortcut target for a Program Menu to open a directory that contains an SDK, so that the user may be able to copy and paste it contents within there application. Shortcut examples I have seen thus far present how to estabilish target shortcut to an exe

[WiX-users] heat.exe: Add attribute Win64="yes" to Component elements?

Hi I am using heat.exe of WiX 3.0. Can it add attribute Win64="yes" to Component elements when it harvests? - Thanks Jeff in Seattle -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-exe-Add-attribute-Win64-yes-to-Component-elements-tp4947

Re: [WiX-users] Install x64-DLL

I just got into this thread. I need to create both x86 and x64 MSI installs, because x86 installs on x64 boxes is messing me up because of the both the registry changes to Wow6432Node and path changes to C:\Program Files (x86)\ So, to create a MSI to be truly x64 installed and not x86 installed

[WiX-users] Resolved: Adding Conditional prevents Source installation even after successful MSI run

The problem had to deal with To fix this problem was to change it to Somehow there was label conflict - Thanks Jeff in Seattle -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-Conditional-prevents-Source-installation-even-after-s

[WiX-users] Adding Conditional prevents Source installation even after successful MSI run

Hi I am having problem with a conditional, whereby it is not installing files. The WiX generated MSI successfully completes: 1. The conditional requirement (tested to make sure it works by putting host in a unpassable state) 2. Shows that product is installed within "Control Panel\All Control Pan

[WiX-users] Dependency Conditionals?

Hi Is there a way to define external product dependency conditionals within WiX authoring, and if this conditional is not meet then do not install? I am creating a WiX for a product that has a dependency to an another product, or it will not run. The dependency product is JDK 32-bit build. When

[WiX-users] Lux: Other tutorials or complete WiX example?

Hi I am writting unit tests to validate install of MSI deliverables, and I am considering to use Lux. I came across Bob Arnson’s blog http://www.joyofsetup.com/2010/02/08/introducing-lux-declarative-unit-testing-for-custom-actions/ Joy of Setup I also looked at http://wix.sourceforge.net/man

Re: [WiX-users] Lux: Other tutorials or complete WiX example?

Hi I all read http://wix.sourceforge.net/manual-wix3/lux.htm WiX Advanced Topics: Unit-testing custom actions with Lux What is not clear to me if Lux can validate if the sources that were used for WiX harvesting match to the installation after MSI installation. - Thanks Jeff in Seattle -

[WiX-users] WiX: Validation after MSI Install?

Hi I read Derek Cicerone's excellent article http://installing.blogspot.com/2006/04/msi-validation-in-wix.html MSI Validation in WiX Is there a way to WiX script so that MSI will validate installation after it has completed its install? Thanks - Thanks Jeff in Seattle -- View this messa

[WiX-users] Conditionals: Host OS Version and Host Processor Type?

Hi Does WiX provide conditionals for restricting install to a. Specific Host OS Version, for example: Can install on Win7, Win2008, WinXP, Win2003, etc... b. Specific Host Processor type, for example: Can only install on 32-Bit, 64-Bi, x86, x64, etc... Thanks - Thanks Jeff in Seattle -- V

Re: [WiX-users] heat.exe warning: limit of 1600 components per feature: what will happen?

Thanks for the reply I compared source and MSI extraction using http://winmerge.org/ WinMerge , and it showed no difference. - Thanks Jeff in Seattle -- View this message in context: http://n2.nabble.com/heat-exe-warning-limit-of-1600-components-per-feature-what-will-happen-tp4928703p4928

[WiX-users] heat.exe warning: limit of 1600 components per feature: what will happen?

heat.exe : warning HEAT5155 : Although there are no limitations to the size of a ComponentGroup, Windows Installer has a limit of 1600 components per feature. Please consider reducing the size of ComponentGroup '$(var.ComponentGroupName)' from current count of '3037'. What is the impact of my ins

[WiX-users] Adding Digital Signature to MSI

Hi Curious, does WiX provide a way to add a digital signature to resulting MSI output? - Thanks Jeff in Seattle -- View this message in context: http://n2.nabble.com/Adding-Digital-Signature-to-MSI-tp4896947p4896947.html Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Suppress "another version of this product is already installed": i.e. install in quite mode

Thanks for the reply, but is there any way to declare with the product's *.wsx file to suppress the dialog "this product is already installed..." if it is already installed? - Thanks Jeff in Seattle -- View this message in context: http://n2.nabble.com/Suppress-another-version-of-this-produ

[WiX-users] Suppress "another version of this product is already installed": i.e. install in quite mode

Hi I want to do a silent (quite) install of a product. Install works great, but when I run the same MSI file again, then dialog message "another version of this product is already installed..." I wish to either: A. Suppress it, i.e. no message and do nothing B. Reinstall quitely I do not know

[WiX-users] NOT listed within "Program and Features"

Hi Within WiX configuration file, how do I modify it so that the when the compiled MSI is called it will NOT list product within "Program and Features"? It is example software solutions, and my customer may request to prevent this action. - Thanks Jeff in Seattle -- View this message in

[WiX-users] How to resolve WiX Warning: "Too Many Components within Feature" ?

Hi I have a project with over 1000 files (1287 to be exact). I created WiS configuration using: > heat dir .\Source -gg -g1 -cg WordPressOnAzure -nologo -sfrag -ke -out > Source.wxs Then I used it within a WiX 3.0 project in Visual Studio 2008. When I built it, the following single warnin

[WiX-users] Heat: How to generate preferred layout style?

Hi I read within some blog pertaining to WiX, is that the preferred layout style is to separate the definition of the directory Directory from the file components that are within it by using DirectoryRef, and listing the components within these. The following heat command-line call combines di