[WiX-users] Setting properties value
Hi, I declared a property in the following way Property Id=VS2012CHECKED / I now need to set the value of this property based on a condition. If the condition is true, the value should be set to 1 else it should be set to NULL. The condition is the following. The property called VS2012DEVENV should not be NULL. How do I achieve that? How to set certain value for a property based on condition? Thanks Mario Majcica -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Pass value from command line to Custom action-Burn
In the bundle.exe define a string Variable element and use bal:Overridable='yes'. Then in MsiPackage use a MsiProperty element to pass the value of the variable into the msi. At that point follow the examples that you found to pass the msi property to your CA, depending on the type of CA. Variable Name='VarName' Type='string' Value='defaultValue' bal:Overridable='yes'/ VarName can have any case you chose. Some folks use the same name as the public property in which case it should be all upper case. Your ba UX could also modify the value of VarName, if needed. MsiProperty Name='MYPROPERTY' Value='[VarName]' / -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Pass-value-from-command-line-to-Custom-action-Burn-tp7598488p7598491.html Sent from the wix-users mailing list archive at Nabble.com. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Always show the option dialog
Can someone point me to some documentation on how to change the UI sequence for a bundle? Thanks, Gary -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Always-show-the-option-dialog-tp7598481p7598495.html Sent from the wix-users mailing list archive at Nabble.com. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Pass value from command line to Custom action-Burn
You'll want to make sure that your CA is scheduled during InstallExecuteSequence and is deferred. Then, set the CustomActionData for that CA, passing it your ENV property that way. However, since you're updating an XML file, then the UtilExtension has XML elements (XmlConfig) to do that, so you wouldn't need a CA at all. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Pass-value-from-command-line-to-Custom-action-Burn-tp7598487p7598494.html Sent from the wix-users mailing list archive at Nabble.com. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Always show the option dialog [P]
Classification: Public Gary I modified the theme file (in my case the RtfTheme.xml) to change the 1 screen to a welcome screen, then changed the options button to a next button, moved the install button to the Options section. (so on the first page I have only two buttons, Next and Cancel) I changed the string loc.InstallOptionsButton Next Then on the Options page I changed it to a EULA page, and have the Install button on that page. (I have three buttons, Back, Install, Cancel) I changed the button text of loc.OptionsOkButton to Back So the install page is a Welcome page The options page is really my EULA page with the install button on that page... Page Name=Install Image X=00 Y=00 Width=160 Height=309 ImageFile=SideBanner.png Visible=no/ Static X=0 Y=309 Width=495 Height=1 HexStyle=0x0200L Visible=no/ Text X=170 Y=20 Width=-11 Height=60 FontId=2 DisablePrefix=yes#(loc.InstallHeader)/Text Text X=170 Y=80 Width=-11 Height=220 FontId=3 DisablePrefix=yes#(loc.InstallMessage)/Text Text X=11 Y=-11 Width=246 Height=17 FontId=4 DisablePrefix=yes#(loc.InstallVersion)/Text Button Name=OptionsButton X=314 Y=-11 Width=75 Height=23 FontId=0 TabStop=yes#(loc.InstallOptionsButton)/Button Button Name=WelcomeCancelButton X=404 Y=-11 Width=75 Height=23 FontId=0 TabStop=yes#(loc.InstallCancelButton)/Button /Page Page Name=Options Image X=00 Y=00 Width=493 Height=58 ImageFile=end-user license.png Visible=no/ Static X=0 Y=309 Width=495 Height=1 HexStyle=0x0200L/ Static X=0 Y=58 Width=495 Height=1 HexStyle=0x0200L/ Text X=11 Y=-11 Width=246 Height=17 FontId=4 DisablePrefix=yes#(loc.InstallVersion)/Text Text X=30 Y=82 Width=444 Height=202 FontId=2 HexStyle=0x0080L/ Richedit Name=EulaRichedit X=31 Y=83 Width=440 Height=198 TabStop=yes FontId=0 / Checkbox Name=EulaAcceptCheckbox X=28 Y=-56 Width=260 Height=17 TabStop=yes FontId=3 HideWhenDisabled=yes#(loc.InstallAcceptCheckbox)/Checkbox Button Name=OptionsOkButton X=238 Y=-11 Width=75 Height=23 TabStop=yes FontId=0#(loc.OptionsOkButton)/Button Button Name=InstallButton X=314 Y=-11 Width=75 Height=23 TabStop=yes FontId=0#(loc.InstallInstallButton)/Button Button Name=WelcomeCancelButton X=404 Y=-11 Width=75 Height=23 TabStop=yes FontId=0#(loc.InstallCloseButton)/Button /Page Cheers, Steve -Original Message- From: garymonk [mailto:g...@gurudental.com] Sent: December-09-14 10:55 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Always show the option dialog Can someone point me to some documentation on how to change the UI sequence for a bundle? Thanks, Gary -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Always-show-the-option-dialog-tp7598481p7598495.html Sent from the wix-users mailing list archive at Nabble.com. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users This message has been marked as Public by Steven Ogilvie on December-09-14 11:05:47 AM. The above classification labels were added to the message by TITUS Message Classification. For more information visit www.titus.com. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Long lasting Installation process. Why?
A verbose log would be useful because of the timestamps so you can see where the time is going. I assume the PDFs are referred to somehow from the MSI file otherwise there would be no need to access them. When you say read, I suspect they're just being accessed for some reason. If the PDFs are available through an MSI feature such as access this feature from the DVD then it's my assumption that the install still goes through things like looking for existing files of that name, costing etc, so the log may show only a long time inside InstallValidate because accessing the DVD is slower. --- Phil Wilson On Tue, Dec 9, 2014 at 3:25 AM, Helmut Ziegler scruffytec...@gmail.com wrote: Hi, we use WIX to deploy an application (100MB) that enables users to browse a big collection of PDF files (around 4 GBs). Installer (setup.msi) and PDFs are distributed via DVD. The PDFs are in a separated directory on the DVD (not part of the setup.msi). The Typical installation is installing the application but leave the PDFs on the DVD. So when using the application PDFs are read from the DVD. With the Custom installation you can install PDF files on your hard disk. Now we found a strange behaviour when running a Typical installation. Although the application is small (100MB) running the installation process lasts very long (about 15 minutes on my computer). On other computers it takes 1 hour. I analyzed the installation (msiexec via ProcessMonitor) and saw that every PDF file that is referenced in the setup.msi is read from DVD (not copied). But I don't know why! Maybe reading these PDFs is a kind of validation behaviour from Window installer. Has anyone has an explanation for this behaviour and knows how to workaround it? Below you find a simplified example that shows how the PDFs are referenced. Cheers, Helmut Feature AllowAdvertise=no Description=It contains the PDFs Id=data_pdf Level=4 Title=PDF ComponentRef Id=component1094/ ... /Feature Directory Id=directory100 Name=data Component Guid=$(var.CompId)01094 Id=component1094 File DiskId=1 Id=file1094 Name=H48729835_00.pdf ShortName=H48729_1.PDF Source=D:\Testing\data\H48729835_00.pdf/ /Component .. /Directory -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??
Hi, Thank you for your quick response. I didn't get this quite clearly. Can you please help? Attached is my bundle.wxs file. There are few thing I am not very sure how to do. Some background before the queries. The bundle.wxs pacages 3 MSI's. Prerequisite(1), ResourceFolder(2) and Final_SF1(3). They are to be called in sequence I mentioned. The only MSI which has GUI and is localized is Final_SF1. This localized MSI's are available in the respective folders (SourceFile=..\Final_SF1\bin\$(var.Platform)\$(var.Configuration)\cs-CZ\Final_SF1.msi) from my build script in respective language folders. I have created fragments as mentioned in earlier reply for few languages. Now the issues. 1. How does I fit these localized MSI's into the sequence of execution? 2. How the bundle knows (or rather I tell bundle) which langaueg Final_SF1 MSI is to be called/executed? 3. And the current code fails to build saying error CNDL0005: The Chain element contains an unexpected child element 'PackageGroup' Am I missing something obvious ? What changes I need to do in my bundle.wxs. Regards, James From: Phill Hogland [via Windows Installer XML (WiX) toolset] ml-node+s687559n759845...@n2.nabble.com To: James unk...@yahoo.com Sent: Friday, 5 December 2014, 11:21 Subject: Re: Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue?? Based on input in this thread I concluded that using embedded transforms would not work in a Burn driven scenario reliably. At the time I had difficulty understanding how to allow the packages to be created with multiple cultures in separate output folders and then pull those back into the bundle. I posted this question and got good advice. http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-external-cab-for-multiple-language-msi-packages-td7596991.html When a package builds, it uses an external cab file, and builds the output of that package project to separate culture named output folders (default behavior of wix). Then in the bundle's I rename the package like this Fragment PackageGroup Id='App' PackageGroupRef Id='App_de_DE'/ PackageGroupRef Id='App_en_US'/ /PackageGroup /Fragment Fragment PackageGroup Id='App_de_DE' MsiPackage Id='App_de_DE' ...stuff... SourceFile='de-DE\App.msi' Name='App\App_de-DE.msi' /MsiPackage /PackageGroup /Fragment Fragment PackageGroup Id='App_en_US' MsiPackage Id='App_en_US' ...stuff... SourceFile='_en_US\App.msi' Name='App\App_en_US.msi' /MsiPackage /PackageGroup /Fragment The packages are not compressed so the renamed msi and related external cab file end up in a sub folder relative to the bundle named App. The tree is much larger than when transforms are used, but since we stage to a server and the customer only gets the small bootstrapper exe (and the packages that their configuration needs), this seems to work for use. Others in this list mentioned using the transforms external to the msi, but I can't speak to that process. If you reply to this email, your message will be added to the discussion below: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7598452.html To unsubscribe from Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??, click here. NAML Bundle.wxs (10K) http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/attachment/7598503/0/Bundle.wxs -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7598503.html Sent from the wix-users mailing list archive at Nabble.com. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??
Define a variable in your bundle, detect the culture in your BA, and set this variable (or use one of the Burn built-in language variables). You could take different approaches here, but the result is that you use the variable in your InstallCondition to determine which of the msi packages will be installed (or use the information in the OnPlanPackageBegin handler to select whether a particular package will be installed or not.) In the example you would replace 'App' with 'Final_SF1', I assume. When you add the following to your chain, all of the PackageGroupRef related to specific cultures, in the example, are included in your chain in the sequence that you authored them. Chain ...Prerequisites ...other stuff PackageGroupRef Id='Final_SF1' Then you need to author the other parameters of the MsiPackage elements so that burn can find the msi packages and you have InstallConditions that specify whether the package is installed. I use the following but you might have different requirements. Variable Name='MyNumericVar' Value='1033' Type='numeric' bal:Overridable='yes'/ I set the var in my ba to an lcid. InstallCondition='MyNumericVar=1031' (true when installing de-DE, otherwise not installed) -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7598508.html Sent from the wix-users mailing list archive at Nabble.com. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wixstdba: Not invoking right msi for 32 bit platform in uninstallation
Hi, One update to understand issue properly. If we provide /log option during installation or un-installation, log file with following name will be created. log file name log file name_incremental number_msi name (on 32 bit) log file name_incremental number_msi name (on 64 bit) example: I am installing product on 32 bit platform. I provided /log setup.txt Then it creates setup.txt and setup_0_a32.txt log files. But during un-installation it creates setup.txt , *setup_0_b64.txt* and setup_1_a32.txt on *32 bit* platform. All the custom action and msi logging is logged in setup_0_b64.txt instead of setup_1_a32.txt This creates the impression that 64 bit msi is invoked during un-installation. In addition to this , on progress screen it shows the name of both 64 bit msi name as well as 32 bit msi name during un-installation. This behavior is not observed on 64 bit platform during un-installation. On 64 bit platform only two log files are created during un-installation. i.e setup.txt and setup_0_b64.txt Is this known/expected behavior? with regards, CD -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wixstdba-Not-invoking-right-msi-for-32-bit-platform-in-uninstallation-tp7598029p7598509.html Sent from the wix-users mailing list archive at Nabble.com. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
