Re: [WiX-users] Wix Burn: Help with silent install (ExePackage
Alright, I tried a different install command according to an example I found in the forum: ExePackage Id=Update SuppressSignatureVerification=yes SourceFile=C:\Downloads\Update_1.12.10.exe PerMachine=yes InstallCommand=/qn UninstallCommand=/qn Vital=no/ It didn't work for me unfortunately. I'm very sorry if I seem a bit slow here, but I don't understand exactly what input InstallCommand needs. I also tried to input the complete msiexec /qn /i command (which works from command line), but no luck. My logfile has this: /Applying execute package: TTUpdate, action: Install, path: C:\Documents and Settings\All Users\Application Data\Package Cache\CC325E7E72D2C044FBEF06359187E9475C1D8D77\Update_1.12.10.exe, arguments: 'C:\Documents and Settings\All Users\Application Data\Package Cache\CC325E7E72D2C044FBEF06359187E9475C1D8D77\Update_1.12.10.exe /qn'/ What am I doing wrong? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Burn-Help-with-silent-install-ExePackage-tp7496163p7498509.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Placement of reboot
Did you reference anything inside the fragment from your main MSI ? If not, see Fragment in the wix help file. -Original Message- From: E. Timothy Uy [mailto:t...@loqu8.com] Sent: 25 April 2012 00:55 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Placement of reboot Perhaps just a misunderstanding. Could it be that CustomActions have to be always between Product/Product and fragments are not exactly extra bits of the Product? On Tue, Apr 24, 2012 at 3:37 PM, Rob Mensching r...@robmensching.com wrote: Because something is wrong? On Tue, Apr 24, 2012 at 2:40 PM, E. Timothy Uy t...@loqu8.com wrote: Here's something strange: CustomAction Id=QtExecInstallCmdLineSet Property=QtExecInstallCmdLineRun Value='[INSTALLFOLDER]xxx.exe install'/ CustomAction Id=QtExecInstallCmdLineRun Impersonate=yes BinaryKey=WixCA DllEntry=CAQuietExec Execute=deferred Return=check / CustomAction Id=QtExecUninstallCmdLineSet Property=QtExecUninstallCmdLineRun Value='[INSTALLFOLDER]xxx.exe uninstall'/ CustomAction Id=QtExecUninstallCmdLineRun Impersonate=yes BinaryKey=WixCA DllEntry=CAQuietExec Execute=deferred Return=check / InstallExecuteSequence Custom Action=QtExecInstallCmdLineSet After=InstallFilesNot Installed/Custom Custom Action=QtExecInstallCmdLineRun After=QtExecInstallCmdLineSetNot Installed/Custom ScheduleReboot After=QtExecInstallCmdLineRun / Custom Action=QtExecUninstallCmdLineSet Before=RemoveFilesInstalled/Custom Custom Action=QtExecUninstallCmdLineRun After=QtExecUninstallCmdLineSetInstalled/Custom /InstallExecuteSequence Placed inside the Product tag, this works, but in a fragment Fragment /Fragment, it does not. Why? Thanks, Tim -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] killing Chrome and Firefox
See Util:CloseApplication in the wix help. -Original Message- From: E. Timothy Uy [mailto:t...@loqu8.com] Sent: 25 April 2012 06:00 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] killing Chrome and Firefox Hi, we are a requirement to kill Chrome and Firefox during install, so that we can install or modify a plugin. What is the best way to kill processes (or ask the user to kill processes)? Thanks, Tim - - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] .Net 4.0 installation feedback using protocol=netfx
Hi - I have set protocol=netfx for the .Net 4.0 ExePackage, and i do get a moving progress bar during its installation. However i wonder if there is a way of showing what the .net installer is actually doing because this can take ages still looks at times like it has hung. I use [ProgressPackageName] which shows me I am processing Microsoft .NET Framework 4, but is there another predefined value to get the actual process being carried out (i.e. copying files..., etc.) ? Thanks. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Net-4-0-installation-feedback-using-protocol-netfx-tp7499137p7499137.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn feedback
Got this working using the steps outlined at http://wix.sourceforge.net/manual-wix3/insignia.htm Target Name=SignBundleEngine Exec Command=quot;C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\signtool.exequot; sign /f privatekey.pfx /p mypassword /t http://timestamp.comodoca.com/authenticode quot;@(SignBundleEngine)quot; / /Target Target Name=SignBundle Exec Command=quot;C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\signtool.exequot; sign /f privatekey.pfx /p mypassword /t http://timestamp.comodoca.com/authenticode quot;@(SignBundle)quot; / /Target I'm also updating all my MSI .wixproj's to use the SignMsi target however it'd be nice if there was a Signing tab in Visual Studio rather than having to manually edit the project files to do things the 'right' way. Feature request for WiX 4.0? Palbinder Sandher Software Platform Engineer T:+44 (0) 141 945 8500 F:+44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: 23 April 2012 13:18 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn feedback Just for info you don't modify wix2010.targets but your wixproj, you are overriding the tasks that are defined in wix2010.targets. This didn't work for me as my certificate is not in the certificate store. Neil Neil Sleightholm n...@x2systems.commailto:n...@x2systems.com On 23 Apr 2012, at 12:48, Pally Sandher wrote: Rob M. others explain how to do it correctly in this thread - http://sourceforge.net/mailarchive/message.php?msg_id=28657655 I haven't attempted to implement this as yet however since it requires modifying the wix2010.targets file but I'll have to look into it sometime this week as I'll need it working for release. Palbinder Sandher Software Platform Engineer T:+44 (0) 141 945 8500 F:+44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: 21 April 2012 14:58 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn feedback You can add signing in the wixproj but I couldn't get that to work and in my case I needed to use signtool as the certificate is not in the certificate store. This is the approach I used (I can't remember to originator of this but it was someone on this list): 1. insignia -ib Setup.exe -o engine.exe 2. signtool engine.exe (extra parameters excluded for simplicity) 3. insignia -ab engine.exe Setup.exe -o Setup.exe 4. signtool Setup.exe (insignia is part of the wix toolset.) Neil -Original Message- From: Rob Diaz [mailto:rob.d...@msxgroup.com] Sent: 20 April 2012 23:05 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Burn feedback I agree that I've had similar troubles. The lack of documentation has made this tougher to do than it should be. Did you find a resolution for the signtool issue? Other than not doing it, I mean. Rob -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Friday, April 20, 2012 5:33 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn feedback Sounds like the same issues I have been having, I am planing to blog about what I have found to help others. Thanks for the LicenceUrl tip, I had missed that and ended up writing my own theme based on the HyperlinkLecense one. Neil Neil Sleightholm n...@x2systems.commailto:n...@x2systems.commailto:n...@x2systems.com On 19 Apr 2012, at 17:34, Pally Sandher wrote: I upgraded to WiX v3.6 from v3.5 earlier this week and started trying to implement Burn as a replacement for dotnetinstaller. So far it's pretty easy to get a chain of packages configured I really like how well done it is (great job everyone involved =) ). A few of the issues I've noticed with it (using v3.6.2816.0): Documentation is very sparse but I guess it's still under construction so it's forgivable but still causes a lot of grief when you're basically left with reverse engineering to discover how to implement things. It makes it very hard to get anywhere with customising it when this is all the documentation you have to follow http://wix.sourceforge.net/manual-wix3/wixstdba_foundation_customization.htm I had to download the sources just to figure out what size to make the logo which this page says you can customise
Re: [WiX-users] Burn - MSIPackage InstallCondition evaluates to false, attempts minor upgrade
More problems with this. This time with MspPackage (code as previous). The
issue is with a system which has already had the MSP applied.
[1428:145C][2012-04-25T14:45:28]: Setting version variable
'SharedContentVersion' to value '2.2.0.0'
[1428:145C][2012-04-25T14:45:29]: Detected package: SharedContentPatch, state:
Present, cached: None
[1428:145C][2012-04-25T14:45:29]: Detected package: SharedContentPatch target:
{92E2C426-6CDB-44D4-8D48-6414A442231D}, state: Present
[1428:145C][2012-04-25T14:45:30]: Condition 'SharedContentVersion v1.9.9.9
AND SharedContentVersion v2.2.0.0' evaluates to false.
[1428:145C][2012-04-25T14:45:30]: Skipping dependency registration on package
with no dependency providers: SharedContentPatch
[1428:145C][2012-04-25T14:45:30]: Planned package: SharedContentPatch, state:
Present, default requested: Absent, ba requested: Absent, execute: Uninstall,
rollback: Install, cache: Yes, uncache: Yes, dependency: None
[0D34:097C][2012-04-25T14:46:46]: Applying package: SharedContentPatch, target:
{92E2C426-6CDB-44D4-8D48-6414A442231D}, action: Uninstall, path: (null),
arguments: '(null)'
[0D34:097C][2012-04-25T14:46:46]: Error 0x8007066e: Failed to uninstall MSP
package.
[0D34:097C][2012-04-25T14:46:46]: Error 0x8007066e: Failed to execute MSP
package.
[1428:145C][2012-04-25T14:46:46]: Error 0x8007066e: Failed to configure
per-machine MSP package.
[1428:145C][2012-04-25T14:46:46]: Applied execute package: SharedContentPatch,
result: 0x8007066e, restart: None
[1428:145C][2012-04-25T14:46:46]: Error 0x8007066e: Failed to execute MSP
package.
Why is it attempting to uninstall the patch when the condition is false the
patch has AllowRemoval=no?
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20
0SP
Email Disclaimer
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: 23 April 2012 11:46
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn - MSIPackage InstallCondition evaluates to false,
attempts minor upgrade
Further to this I'm also getting no UI for the MSP package below even though
DisplayInternalUI=yes. Not a massive issue just a bit different to what I was
expecting. It upgrades perfectly fine.
Palbinder Sandher
Software Platform Engineer
T:+44 (0) 141 945 8500
F:+44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20
0SP
Email Disclaimer
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: 19 April 2012 17:00
To: General discussion for Windows Installer XML toolset.
(wix-users@lists.sourceforge.net)
Subject: [WiX-users] Burn - MSIPackage InstallCondition evaluates to false,
attempts minor upgrade
Relevant parts of my code:
util:ProductSearch Id=SharedContent
Variable=SharedContentVersion
Guid=92E2C426-6CDB-44D4-8D48-6414A442231D
Result=version /
MsiPackage Id=SharedContentFull
SourceFile=..\..\..\install\VESharedContent.msi
After=NET4.0
Compressed=no
DisplayInternalUI=yes
DownloadUrl=http://removed/VESharedContent.msi;
ForcePerMachine=yes
Visible=yes
Vital=yes
InstallCondition=SharedContentVersion lt; v2.0.0.0 /
MspPackage Id=SharedContentPatch
SourceFile=..\..\..\install\VESharedContent.msp
After=SharedContentFull
Compressed=no
DisplayInternalUI=yes
DownloadUrl=http://removed/VESharedContent.msp;
PerMachine=yes
Vital=yes
InstallCondition=SharedContentVersion gt; v1.9.9.9 AND
SharedContentVersion lt; v2.2.0.0 /
Relevant parts of the log:
[07FC:082C][2012-04-19T15:52:19]: Setting version variable
'SharedContentVersion' to value '2.1.0.0'
[07FC:082C][2012-04-19T15:52:19]: Calculating patch applicability for target
product code: {92E2C426-6CDB-44D4-8D48-6414A442231D}, context: Machine
[07FC:082C][2012-04-19T15:52:21]: Detected related package:
{92E2C426-6CDB-44D4-8D48-6414A442231D}, scope: PerMachine, version: 2.1.0.0,
language: 1033 operation: MinorUpdate
[07FC:082C][2012-04-19T15:52:21]: Detected package: SharedContentFull, state:
Present, cached: None
[07FC:082C][2012-04-19T15:52:21]: Detected package: SharedContentPatch, state:
Absent, cached: None
[WiX-users] Bundle failing to build after upgrading to latest release (3.6.2823)
Upgraded from WiX v3.6.2816 to v3.6.2823. Haven't changed anything in source. MSI's build fine but my burn bundle fails now. Log is as follows: -- Rebuild All started: Project: VESetup, Configuration: Release x86 -- Deleting file obj\Release\Bundle.wixobj. C:\Program Files (x86)\WiX Toolset v3.6\bin\candle.exe -v -dDevEnvDir=C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\\ -dSolutionDir=D:\Users\dev.build\pSource\csi_main\code\VEInstall\ -dSolutionExt=.sln -dSolutionFileName=VEInstall.sln -dSolutionName=VEInstall -dSolutionPath=D:\Users\dev.build\pSource\csi_main\code\VEInstall\VEInstall.sln -dConfiguration=Release -dOutDir=D:\Users\dev.build\pSource\csi_main\code\VEInstall\..\..\install\ -dPlatform=x86 -dProjectDir=D:\Users\dev.build\pSource\csi_main\code\VEInstall\VESetup\ -dProjectExt=.wixproj -dProjectFileName=VESetup.wixproj -dProjectName=VESetup -dProjectPath=D:\Users\dev.build\pSource\csi_main\code\VEInstall\VESetup\VESetup.wixproj -dTargetDir=D:\Users\dev.build\pSource\csi_main\install\ -dTargetExt=.exe -dTargetFileName=ve65setup.exe -dTargetName=ve65setup -dTargetPath=D:\Users\dev.build\pSource\csi_main\install\ve65setup.exe -out obj\Release\ -arch x86 -ext C:\Program Files (x86)\WiX Toolset v3.6\bin\\WixUtilExtension.dll -ext C:\Program Files (x86)\WiX Toolset v3.6\bin\\WixBalExtension.dll Bundle.wxs Microsoft (R) Windows Installer Xml Compiler version 3.6.2823.0 Copyright (C) Microsoft Corporation. All rights reserved. Bundle.wxs C:\Program Files (x86)\WiX Toolset v3.6\bin\Light.exe -out D:\Users\dev.build\pSource\csi_main\install\ve65setup.exe -pdbout D:\Users\dev.build\pSource\csi_main\install\ve65setup.wixpdb -v -ext C:\Program Files (x86)\WiX Toolset v3.6\bin\\WixUtilExtension.dll -ext C:\Program Files (x86)\WiX Toolset v3.6\bin\\WixBalExtension.dll -spdb -contentsfile obj\Release\VESetup.wixproj.BindContentsFileList.txt -outputsfile obj\Release\VESetup.wixproj.BindOutputsFileList.txt -builtoutputsfile obj\Release\VESetup.wixproj.BindBuiltOutputsFileList.txt obj\Release\Bundle.wixobj Microsoft (R) Windows Installer Xml Linker version 3.6.2823.0 Copyright (C) Microsoft Corporation. All rights reserved. light.exe(0,0): error LGHT0001: An item with the same key has already been added. Exception Type: System.ArgumentException Stack Trace: at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource) at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add) at System.Collections.ObjectModel.KeyedCollection`2.AddKey(TKey key, TItem item) at System.Collections.ObjectModel.KeyedCollection`2.InsertItem(Int32 index, TItem item) at System.Collections.ObjectModel.Collection`1.Add(T item) at Microsoft.Tools.WindowsInstallerXml.Binder.ChainPackageInfo.ResolveMspPackage(BinderCore core, Output bundle) at Microsoft.Tools.WindowsInstallerXml.Binder.ChainPackageInfo..ctor(String id, String packageType, String payloadId, String installCondition, String installCommand, String repairCommand, String uninstallCommand, Object cacheData, String cacheId, Object attributesData, Object vitalData, Object perMachineData, String detectCondition, String msuKB, Object repairableData, String logPathVariable, String rollbackPathVariable, String protocol, Int32 installSize, Object suppressLooseFilePayloadGenerationData, Object enableFeatureSelectionData, Object forcePerMachineData, Object displayInternalUIData, Table wixGroupTable, Dictionary`2 allPayloads, Dictionary`2 containers, BinderFileManager fileManager, BinderCore core, Output bundle) at Microsoft.Tools.WindowsInstallerXml.Binder.ChainPackageInfo..ctor(Row row, Table wixGroupTable, Dictionary`2 allPayloads, Dictionary`2 containers, BinderFileManager fileManager, BinderCore core, Output bundle) at Microsoft.Tools.WindowsInstallerXml.Binder.BindBundle(Output bundle, String bundleFile) at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output output, String file) at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args) Binder temporary directory located at 'C:\Users\dev.build\AppData\Local\Temp\zdrijwlv'. Done building project VESetup.wixproj -- FAILED. == Rebuild All: 0 succeeded, 1 failed, 0 skipped == XML is as follows: ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:bal=http://schemas.microsoft.com/wix/BalExtension; xmlns:util=http://schemas.microsoft.com/wix/UtilExtension; Bundle Name=IES Virtual Environment 2012 Version=12.1.0.0 Manufacturer=Integrated Environmental
Re: [WiX-users] .Net 4.0 installation feedback using protocol=netfx
Unfortunately, that is a feature request you need to send to the NETFX team. We are getting everything we can out of the netfx protocol. On Wed, Apr 25, 2012 at 4:57 AM, stewarth stewart.hil...@thomsonreuters.com wrote: Hi - I have set protocol=netfx for the .Net 4.0 ExePackage, and i do get a moving progress bar during its installation. However i wonder if there is a way of showing what the .net installer is actually doing because this can take ages still looks at times like it has hung. I use [ProgressPackageName] which shows me I am processing Microsoft .NET Framework 4, but is there another predefined value to get the actual process being carried out (i.e. copying files..., etc.) ? Thanks. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Net-4-0-installation-feedback-using-protocol-netfx-tp7499137p7499137.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Changing reboot message
It very much depends how you structure your .wxs code. On Tue, Apr 24, 2012 at 4:53 PM, E. Timothy Uy t...@loqu8.com wrote: Thanks Rob! I added ?xml version=1.0 encoding=utf-8? WixLocalization Culture=en-us xmlns= http://schemas.microsoft.com/wix/2006/localization; String Id=Error1703[2] has been installed. Click Yes to restart now. Click No to manually restart later/String /WixLocalization Which ultimately worked, though it did send my output to bin\Release\en-us. Is the localization file the only way to do this? I wasn't able to add just the string into my main wxs. Respectfully, Tim On Tue, Apr 24, 2012 at 3:37 PM, Rob Mensching r...@robmensching.com wrote: Add an Error element. On Tue, Apr 24, 2012 at 9:54 AM, E. Timothy Uy t...@loqu8.com wrote: Is it possible to change the reboot message shown for ScheduleReboot? I would like it to be simpler, something like [2] has been installed. Click Yes to restart now. Click No to manually restart later. I read of some folks using Error Id=1703 but I'm not sure where to put this. Respectfully, Tim -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn - MSIPackage InstallCondition evaluates to false, attempts minor upgrade
On 25-Apr-12 10:06, Pally Sandher wrote: Why is it attempting to uninstall the patch when the condition is false the patch has AllowRemoval=no? Because Burn always attempts to uninstall a package that's present when its install condition is false, and Burn doesn't know the patch is permanent. You can file a feature request to change either of those facts or consider using patch applicability instead of install conditions to control the patch installation. -- sig://boB http://joyofsetup.com/ -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bundle failing to build after upgrading to latest release (3.6.2823)
On 25-Apr-12 11:45, Pally Sandher wrote: Microsoft (R) Windows Installer Xml Linker version 3.6.2823.0 Copyright (C) Microsoft Corporation. All rights reserved. light.exe(0,0): error LGHT0001: An item with the same key has already been added. Exception Type: System.ArgumentException That's bad. Can you unzip the .pdbs into your WiX directory to get line numbers and file a bug? -- sig://boB http://joyofsetup.com/ -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using property when creating directory
Define your directory like this: Directory Id=WEBSITEDIRNAME And don't create a property for WEBSITEDIRNAME. Essentially all directory ids behave like properties. Since you need to change the directory with a control that requires a public property so the directory id must be all uppercase. Edwin G. Castro Software Developer - Staff Digital Channels Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: b.p.fal...@accenture.com [mailto:b.p.fal...@accenture.com] Sent: Tuesday, April 24, 2012 9:28 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Using property when creating directory I have a property bound to control, named WEBSITEDIRNAME, and I would like to use the value when creating a Directory Id=WebSiteDirNameId instead of static Name value. Regards, Benjamin Fallar III | Microsoft Developer Lead Avanade Software Cloud Services (ASCS) Accenture | Manila Plan Ahead. Be Ahead. Plan BCM. www.accenture.com Subject to local law, communications with Accenture and its affiliates including telephone calls and emails (including content), may be monitored by our systems for the purposes of security and the assessment of internal compliance with Accenture policy. __ www.accenture.com -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] killing Chrome and Firefox
Looks like I can only use WixCloseApplications once. How do I close all browsers both before installation and right before uninstallation? Trying the following... util:CloseApplication Id=CloseIE CloseMessage=no Description=Internet Explorer is still running. ElevatedCloseMessage=no RebootPrompt=no Target=iexplore.exe/ util:CloseApplication Id=CloseChrome CloseMessage=no Description=Chrome is still running. ElevatedCloseMessage=no RebootPrompt=no Target=chrome.exe/ util:CloseApplication Id=CloseFirefox CloseMessage=no Description=Chrome is still running. ElevatedCloseMessage=no RebootPrompt=no Target=firefox.exe/ InstallExecuteSequence Custom Action=WixCloseApplications Before=LaunchConditions / On Wed, Apr 25, 2012 at 2:03 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote: See Util:CloseApplication in the wix help. -Original Message- From: E. Timothy Uy [mailto:t...@loqu8.com] Sent: 25 April 2012 06:00 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] killing Chrome and Firefox Hi, we are a requirement to kill Chrome and Firefox during install, so that we can install or modify a plugin. What is the best way to kill processes (or ask the user to kill processes)? Thanks, Tim - - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] killing Chrome and Firefox
By the way, the code below doesn't work at all. On Wed, Apr 25, 2012 at 12:02 PM, E. Timothy Uy t...@loqu8.com wrote: Looks like I can only use WixCloseApplications once. How do I close all browsers both before installation and right before uninstallation? Trying the following... util:CloseApplication Id=CloseIE CloseMessage=no Description=Internet Explorer is still running. ElevatedCloseMessage=no RebootPrompt=no Target=iexplore.exe/ util:CloseApplication Id=CloseChrome CloseMessage=no Description=Chrome is still running. ElevatedCloseMessage=no RebootPrompt=no Target=chrome.exe/ util:CloseApplication Id=CloseFirefox CloseMessage=no Description=Chrome is still running. ElevatedCloseMessage=no RebootPrompt=no Target=firefox.exe/ InstallExecuteSequence Custom Action=WixCloseApplications Before=LaunchConditions / On Wed, Apr 25, 2012 at 2:03 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote: See Util:CloseApplication in the wix help. -Original Message- From: E. Timothy Uy [mailto:t...@loqu8.com] Sent: 25 April 2012 06:00 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] killing Chrome and Firefox Hi, we are a requirement to kill Chrome and Firefox during install, so that we can install or modify a plugin. What is the best way to kill processes (or ask the user to kill processes)? Thanks, Tim - - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Placement of reboot
Ahh, I'm sure that was it. A Fragment that does not get referenced does not got run correct? On Wed, Apr 25, 2012 at 1:50 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote: Did you reference anything inside the fragment from your main MSI ? If not, see Fragment in the wix help file. -Original Message- From: E. Timothy Uy [mailto:t...@loqu8.com] Sent: 25 April 2012 00:55 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Placement of reboot Perhaps just a misunderstanding. Could it be that CustomActions have to be always between Product/Product and fragments are not exactly extra bits of the Product? On Tue, Apr 24, 2012 at 3:37 PM, Rob Mensching r...@robmensching.com wrote: Because something is wrong? On Tue, Apr 24, 2012 at 2:40 PM, E. Timothy Uy t...@loqu8.com wrote: Here's something strange: CustomAction Id=QtExecInstallCmdLineSet Property=QtExecInstallCmdLineRun Value='[INSTALLFOLDER]xxx.exe install'/ CustomAction Id=QtExecInstallCmdLineRun Impersonate=yes BinaryKey=WixCA DllEntry=CAQuietExec Execute=deferred Return=check / CustomAction Id=QtExecUninstallCmdLineSet Property=QtExecUninstallCmdLineRun Value='[INSTALLFOLDER]xxx.exe uninstall'/ CustomAction Id=QtExecUninstallCmdLineRun Impersonate=yes BinaryKey=WixCA DllEntry=CAQuietExec Execute=deferred Return=check / InstallExecuteSequence Custom Action=QtExecInstallCmdLineSet After=InstallFilesNot Installed/Custom Custom Action=QtExecInstallCmdLineRun After=QtExecInstallCmdLineSetNot Installed/Custom ScheduleReboot After=QtExecInstallCmdLineRun / Custom Action=QtExecUninstallCmdLineSet Before=RemoveFilesInstalled/Custom Custom Action=QtExecUninstallCmdLineRun After=QtExecUninstallCmdLineSetInstalled/Custom /InstallExecuteSequence Placed inside the Product tag, this works, but in a fragment Fragment /Fragment, it does not. Why? Thanks, Tim -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all
Re: [WiX-users] killing Chrome and Firefox
I changed WixCloseApplications to run before InstallInitialize but this did not help either. From the .msi log, I see Action 12:12:49: WixCloseApplications. Action start 12:12:49: WixCloseApplications. Action ended 12:12:50: WixCloseApplications. Return value 1. Action 12:12:50: InstallInitialize. Action start 12:12:50: InstallInitialize. Action ended 12:12:55: InstallInitialize. Return value 1. I expected some kind of dialog saying I had these applications open, and for the installer to either shut them down or prompt me to shutdown, but no browsers get closed and there is no indication of any changes. UI DialogRef Id=FilesInUse / DialogRef Id=MsiRMFilesInUse / UIRef Id=WixUI_InstallDir / UIRef Id=WixUI_ErrorProgressText / /UI InstallExecuteSequence Custom Action=WixCloseApplications Before=InstallInitialize / Custom Action=QtExecInstallCmdLineSet After=InstallFilesNot Installed/Custom Custom Action=QtExecInstallCmdLineRun After=QtExecInstallCmdLineSetNot Installed/Custom ScheduleReboot After=QtExecInstallCmdLineRun / Custom Action=QtExecUninstallCmdLineSet Before=RemoveFilesInstalled/Custom Custom Action=QtExecUninstallCmdLineRun After=QtExecUninstallCmdLineSetInstalled/Custom /InstallExecuteSequence util:CloseApplication Id=CloseIE CloseMessage=no Description=Internet Explorer is still running. ElevatedCloseMessage=no RebootPrompt=no Target=iexplore.exe/ util:CloseApplication Id=CloseChrome CloseMessage=no Description=Chrome is still running. ElevatedCloseMessage=no RebootPrompt=no Target=chrome.exe/ util:CloseApplication Id=CloseFirefox CloseMessage=no Description=Chrome is still running. ElevatedCloseMessage=no RebootPrompt=no Target=firefox.exe/ On Wed, Apr 25, 2012 at 12:04 PM, E. Timothy Uy t...@loqu8.com wrote: By the way, the code below doesn't work at all. On Wed, Apr 25, 2012 at 12:02 PM, E. Timothy Uy t...@loqu8.com wrote: Looks like I can only use WixCloseApplications once. How do I close all browsers both before installation and right before uninstallation? Trying the following... util:CloseApplication Id=CloseIE CloseMessage=no Description=Internet Explorer is still running. ElevatedCloseMessage=no RebootPrompt=no Target=iexplore.exe/ util:CloseApplication Id=CloseChrome CloseMessage=no Description=Chrome is still running. ElevatedCloseMessage=no RebootPrompt=no Target=chrome.exe/ util:CloseApplication Id=CloseFirefox CloseMessage=no Description=Chrome is still running. ElevatedCloseMessage=no RebootPrompt=no Target=firefox.exe/ InstallExecuteSequence Custom Action=WixCloseApplications Before=LaunchConditions / On Wed, Apr 25, 2012 at 2:03 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote: See Util:CloseApplication in the wix help. -Original Message- From: E. Timothy Uy [mailto:t...@loqu8.com] Sent: 25 April 2012 06:00 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] killing Chrome and Firefox Hi, we are a requirement to kill Chrome and Firefox during install, so that we can install or modify a plugin. What is the best way to kill processes (or ask the user to kill processes)? Thanks, Tim - - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK.
Re: [WiX-users] Placement of reboot
Run wouldn't be the proper term. It's more including the fragment when it compiles the MSI. If it isn't referenced, then it doesn't exist. -Original Message- From: E. Timothy Uy [mailto:t...@loqu8.com] Sent: Wednesday, April 25, 2012 2:15 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Placement of reboot Ahh, I'm sure that was it. A Fragment that does not get referenced does not got run correct? On Wed, Apr 25, 2012 at 1:50 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote: Did you reference anything inside the fragment from your main MSI ? If not, see Fragment in the wix help file. -Original Message- From: E. Timothy Uy [mailto:t...@loqu8.com] Sent: 25 April 2012 00:55 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Placement of reboot Perhaps just a misunderstanding. Could it be that CustomActions have to be always between Product/Product and fragments are not exactly extra bits of the Product? On Tue, Apr 24, 2012 at 3:37 PM, Rob Mensching r...@robmensching.com wrote: Because something is wrong? On Tue, Apr 24, 2012 at 2:40 PM, E. Timothy Uy t...@loqu8.com wrote: Here's something strange: CustomAction Id=QtExecInstallCmdLineSet Property=QtExecInstallCmdLineRun Value='[INSTALLFOLDER]xxx.exe install'/ CustomAction Id=QtExecInstallCmdLineRun Impersonate=yes BinaryKey=WixCA DllEntry=CAQuietExec Execute=deferred Return=check / CustomAction Id=QtExecUninstallCmdLineSet Property=QtExecUninstallCmdLineRun Value='[INSTALLFOLDER]xxx.exe uninstall'/ CustomAction Id=QtExecUninstallCmdLineRun Impersonate=yes BinaryKey=WixCA DllEntry=CAQuietExec Execute=deferred Return=check / InstallExecuteSequence Custom Action=QtExecInstallCmdLineSet After=InstallFilesNot Installed/Custom Custom Action=QtExecInstallCmdLineRun After=QtExecInstallCmdLineSetNot Installed/Custom ScheduleReboot After=QtExecInstallCmdLineRun / Custom Action=QtExecUninstallCmdLineSet Before=RemoveFilesInstalled/Custom Custom Action=QtExecUninstallCmdLineRun After=QtExecUninstallCmdLineSetInstalled/Custom /InstallExecuteSequence Placed inside the Product tag, this works, but in a fragment Fragment /Fragment, it does not. Why? Thanks, Tim -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats.
Re: [WiX-users] killing Chrome and Firefox
Silly me. I was able to get the browsers to close by setting CloseMessage=yes. Next step, how do I use FilesInUse? On Wed, Apr 25, 2012 at 12:18 PM, E. Timothy Uy t...@loqu8.com wrote: I changed WixCloseApplications to run before InstallInitialize but this did not help either. From the .msi log, I see Action 12:12:49: WixCloseApplications. Action start 12:12:49: WixCloseApplications. Action ended 12:12:50: WixCloseApplications. Return value 1. Action 12:12:50: InstallInitialize. Action start 12:12:50: InstallInitialize. Action ended 12:12:55: InstallInitialize. Return value 1. I expected some kind of dialog saying I had these applications open, and for the installer to either shut them down or prompt me to shutdown, but no browsers get closed and there is no indication of any changes. UI DialogRef Id=FilesInUse / DialogRef Id=MsiRMFilesInUse / UIRef Id=WixUI_InstallDir / UIRef Id=WixUI_ErrorProgressText / /UI InstallExecuteSequence Custom Action=WixCloseApplications Before=InstallInitialize / Custom Action=QtExecInstallCmdLineSet After=InstallFilesNot Installed/Custom Custom Action=QtExecInstallCmdLineRun After=QtExecInstallCmdLineSetNot Installed/Custom ScheduleReboot After=QtExecInstallCmdLineRun / Custom Action=QtExecUninstallCmdLineSet Before=RemoveFilesInstalled/Custom Custom Action=QtExecUninstallCmdLineRun After=QtExecUninstallCmdLineSetInstalled/Custom /InstallExecuteSequence util:CloseApplication Id=CloseIE CloseMessage=no Description=Internet Explorer is still running. ElevatedCloseMessage=no RebootPrompt=no Target=iexplore.exe/ util:CloseApplication Id=CloseChrome CloseMessage=no Description=Chrome is still running. ElevatedCloseMessage=no RebootPrompt=no Target=chrome.exe/ util:CloseApplication Id=CloseFirefox CloseMessage=no Description=Chrome is still running. ElevatedCloseMessage=no RebootPrompt=no Target=firefox.exe/ On Wed, Apr 25, 2012 at 12:04 PM, E. Timothy Uy t...@loqu8.com wrote: By the way, the code below doesn't work at all. On Wed, Apr 25, 2012 at 12:02 PM, E. Timothy Uy t...@loqu8.com wrote: Looks like I can only use WixCloseApplications once. How do I close all browsers both before installation and right before uninstallation? Trying the following... util:CloseApplication Id=CloseIE CloseMessage=no Description=Internet Explorer is still running. ElevatedCloseMessage=no RebootPrompt=no Target=iexplore.exe/ util:CloseApplication Id=CloseChrome CloseMessage=no Description=Chrome is still running. ElevatedCloseMessage=no RebootPrompt=no Target=chrome.exe/ util:CloseApplication Id=CloseFirefox CloseMessage=no Description=Chrome is still running. ElevatedCloseMessage=no RebootPrompt=no Target=firefox.exe/ InstallExecuteSequence Custom Action=WixCloseApplications Before=LaunchConditions / On Wed, Apr 25, 2012 at 2:03 AM, Peter Shirtcliffe pshirtcli...@sdl.com wrote: See Util:CloseApplication in the wix help. -Original Message- From: E. Timothy Uy [mailto:t...@loqu8.com] Sent: 25 April 2012 06:00 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] killing Chrome and Firefox Hi, we are a requirement to kill Chrome and Firefox during install, so that we can install or modify a plugin. What is the best way to kill processes (or ask the user to kill processes)? Thanks, Tim - - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company
Re: [WiX-users] Placement of reboot
On 25/04/2012 20:33, Hoover, Jacob wrote: Run wouldn't be the proper term. It's more including the fragment when it compiles the MSI. If it isn't referenced, then it doesn't exist. I don't think 'compile' is the proper term either - I think it happens during linking :) -- Bruce Cran -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] MsiRMFilesInUse example to restart browsers
Dear Rob et al., Thanks everyone for being so gracious. This time I would like the installer to shutdown any browsers (IE, Chrome, Firefox) prior to installation, and restart them after installation completes. I think I should use MsiRMFilesInUse but have not been able to locate any samples or instructions. Is this used with util:CloseApplication? I gather that I need DialogRef Id=MsiRMFilesInUse / in UI. Can I use WixUI_InstallDir or should I be using Mondo? A completed example would be ideal. The How To Guides are fantastic. Respectfully, Tim -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MsiRMFilesInUse example to restart browsers
Looks like RM only works with Vista+. What is the fallback for XP? On Wed, Apr 25, 2012 at 1:53 PM, E. Timothy Uy t...@loqu8.com wrote: Dear Rob et al., Thanks everyone for being so gracious. This time I would like the installer to shutdown any browsers (IE, Chrome, Firefox) prior to installation, and restart them after installation completes. I think I should use MsiRMFilesInUse but have not been able to locate any samples or instructions. Is this used with util:CloseApplication? I gather that I need DialogRef Id=MsiRMFilesInUse / in UI. Can I use WixUI_InstallDir or should I be using Mondo? A completed example would be ideal. The How To Guides are fantastic. Respectfully, Tim -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MsiRMFilesInUse example to restart browsers
I was able to show the FilesInUse (for iexplore, chrome and firefox) but just adding util:RestartResource Id=RestartIE ProcessName=iexplore.exe / util:RestartResource Id=RestartChrome ProcessName=chrome.exe / util:RestartResource Id=RestartFirefox ProcessName=firefox.exe / However, clicking on attempt to close prompted me with The setup was unable to automatically close all requested applications. Please ensure that the applications holding files in use are closed before continuing with the installation. None of the browser instances are closed. Any advice would be much appreciated. Respectfully, Tim On Wed, Apr 25, 2012 at 1:56 PM, E. Timothy Uy t...@loqu8.com wrote: Looks like RM only works with Vista+. What is the fallback for XP? On Wed, Apr 25, 2012 at 1:53 PM, E. Timothy Uy t...@loqu8.com wrote: Dear Rob et al., Thanks everyone for being so gracious. This time I would like the installer to shutdown any browsers (IE, Chrome, Firefox) prior to installation, and restart them after installation completes. I think I should use MsiRMFilesInUse but have not been able to locate any samples or instructions. Is this used with util:CloseApplication? I gather that I need DialogRef Id=MsiRMFilesInUse / in UI. Can I use WixUI_InstallDir or should I be using Mondo? A completed example would be ideal. The How To Guides are fantastic. Respectfully, Tim -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MsiRMFilesInUse example to restart browsers
The plot thickens. Removing Chrome from the mix makes it work. util:RestartResource Id=RestartIE ProcessName=iexplore.exe / util:RestartResource Id=RestartFirefox ProcessName=firefox.exe / Is this solvable? I did notice that chrome.exe uses a lot of processes. Could this be the issue? Is there a limit on the # of processes? On Wed, Apr 25, 2012 at 2:14 PM, E. Timothy Uy t...@loqu8.com wrote: I was able to show the FilesInUse (for iexplore, chrome and firefox) but just adding util:RestartResource Id=RestartIE ProcessName=iexplore.exe / util:RestartResource Id=RestartChrome ProcessName=chrome.exe / util:RestartResource Id=RestartFirefox ProcessName=firefox.exe / However, clicking on attempt to close prompted me with The setup was unable to automatically close all requested applications. Please ensure that the applications holding files in use are closed before continuing with the installation. None of the browser instances are closed. Any advice would be much appreciated. Respectfully, Tim On Wed, Apr 25, 2012 at 1:56 PM, E. Timothy Uy t...@loqu8.com wrote: Looks like RM only works with Vista+. What is the fallback for XP? On Wed, Apr 25, 2012 at 1:53 PM, E. Timothy Uy t...@loqu8.com wrote: Dear Rob et al., Thanks everyone for being so gracious. This time I would like the installer to shutdown any browsers (IE, Chrome, Firefox) prior to installation, and restart them after installation completes. I think I should use MsiRMFilesInUse but have not been able to locate any samples or instructions. Is this used with util:CloseApplication? I gather that I need DialogRef Id=MsiRMFilesInUse / in UI. Can I use WixUI_InstallDir or should I be using Mondo? A completed example would be ideal. The How To Guides are fantastic. Respectfully, Tim -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MsiRMFilesInUse example to restart browsers
chrome.exe - does not close firefox.exe - closes, but never restarts iexplore.exe - closes and restarts (blank page) On Wed, Apr 25, 2012 at 2:50 PM, E. Timothy Uy t...@loqu8.com wrote: The plot thickens. Removing Chrome from the mix makes it work. util:RestartResource Id=RestartIE ProcessName=iexplore.exe / util:RestartResource Id=RestartFirefox ProcessName=firefox.exe / Is this solvable? I did notice that chrome.exe uses a lot of processes. Could this be the issue? Is there a limit on the # of processes? On Wed, Apr 25, 2012 at 2:14 PM, E. Timothy Uy t...@loqu8.com wrote: I was able to show the FilesInUse (for iexplore, chrome and firefox) but just adding util:RestartResource Id=RestartIE ProcessName=iexplore.exe / util:RestartResource Id=RestartChrome ProcessName=chrome.exe / util:RestartResource Id=RestartFirefox ProcessName=firefox.exe / However, clicking on attempt to close prompted me with The setup was unable to automatically close all requested applications. Please ensure that the applications holding files in use are closed before continuing with the installation. None of the browser instances are closed. Any advice would be much appreciated. Respectfully, Tim On Wed, Apr 25, 2012 at 1:56 PM, E. Timothy Uy t...@loqu8.com wrote: Looks like RM only works with Vista+. What is the fallback for XP? On Wed, Apr 25, 2012 at 1:53 PM, E. Timothy Uy t...@loqu8.com wrote: Dear Rob et al., Thanks everyone for being so gracious. This time I would like the installer to shutdown any browsers (IE, Chrome, Firefox) prior to installation, and restart them after installation completes. I think I should use MsiRMFilesInUse but have not been able to locate any samples or instructions. Is this used with util:CloseApplication? I gather that I need DialogRef Id=MsiRMFilesInUse / in UI. Can I use WixUI_InstallDir or should I be using Mondo? A completed example would be ideal. The How To Guides are fantastic. Respectfully, Tim -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] killing Chrome and Firefox
It seems that CloseMessage=no should have triggered FilesInUse, but it doesn't at all. The installation just proceeds. On Wed, Apr 25, 2012 at 1:05 PM, E. Timothy Uy t...@loqu8.com wrote: Silly me. I was able to get the browsers to close by setting CloseMessage=yes. Next step, how do I use FilesInUse? On Wed, Apr 25, 2012 at 12:18 PM, E. Timothy Uy t...@loqu8.com wrote: I changed WixCloseApplications to run before InstallInitialize but this did not help either. From the .msi log, I see Action 12:12:49: WixCloseApplications. Action start 12:12:49: WixCloseApplications. Action ended 12:12:50: WixCloseApplications. Return value 1. Action 12:12:50: InstallInitialize. Action start 12:12:50: InstallInitialize. Action ended 12:12:55: InstallInitialize. Return value 1. I expected some kind of dialog saying I had these applications open, and for the installer to either shut them down or prompt me to shutdown, but no browsers get closed and there is no indication of any changes. UI DialogRef Id=FilesInUse / DialogRef Id=MsiRMFilesInUse / UIRef Id=WixUI_InstallDir / UIRef Id=WixUI_ErrorProgressText / /UI InstallExecuteSequence Custom Action=WixCloseApplications Before=InstallInitialize / Custom Action=QtExecInstallCmdLineSet After=InstallFilesNot Installed/Custom Custom Action=QtExecInstallCmdLineRun After=QtExecInstallCmdLineSetNot Installed/Custom ScheduleReboot After=QtExecInstallCmdLineRun / Custom Action=QtExecUninstallCmdLineSet Before=RemoveFilesInstalled/Custom Custom Action=QtExecUninstallCmdLineRun After=QtExecUninstallCmdLineSetInstalled/Custom /InstallExecuteSequence util:CloseApplication Id=CloseIE CloseMessage=no Description=Internet Explorer is still running. ElevatedCloseMessage=no RebootPrompt=no Target=iexplore.exe/ util:CloseApplication Id=CloseChrome CloseMessage=no Description=Chrome is still running. ElevatedCloseMessage=no RebootPrompt=no Target=chrome.exe/ util:CloseApplication Id=CloseFirefox CloseMessage=no Description=Chrome is still running. ElevatedCloseMessage=no RebootPrompt=no Target=firefox.exe/ On Wed, Apr 25, 2012 at 12:04 PM, E. Timothy Uy t...@loqu8.com wrote: By the way, the code below doesn't work at all. On Wed, Apr 25, 2012 at 12:02 PM, E. Timothy Uy t...@loqu8.com wrote: Looks like I can only use WixCloseApplications once. How do I close all browsers both before installation and right before uninstallation? Trying the following... util:CloseApplication Id=CloseIE CloseMessage=no Description=Internet Explorer is still running. ElevatedCloseMessage=no RebootPrompt=no Target=iexplore.exe/ util:CloseApplication Id=CloseChrome CloseMessage=no Description=Chrome is still running. ElevatedCloseMessage=no RebootPrompt=no Target=chrome.exe/ util:CloseApplication Id=CloseFirefox CloseMessage=no Description=Chrome is still running. ElevatedCloseMessage=no RebootPrompt=no Target=firefox.exe/ InstallExecuteSequence Custom Action=WixCloseApplications Before=LaunchConditions / On Wed, Apr 25, 2012 at 2:03 AM, Peter Shirtcliffe pshirtcli...@sdl.com wrote: See Util:CloseApplication in the wix help. -Original Message- From: E. Timothy Uy [mailto:t...@loqu8.com] Sent: 25 April 2012 06:00 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] killing Chrome and Firefox Hi, we are a requirement to kill Chrome and Firefox during install, so that we can install or modify a plugin. What is the best way to kill processes (or ask the user to kill processes)? Thanks, Tim - - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of
[WiX-users] Upgrade a product with add-ons without requiring a reboot?
A long time ago our company released a product, let's call it Product 1.0. A little while later we released an add-on, let's call it Add-On 1.0. Now we are releasing Product 1.5. However we decided that for this version Add-On 1.5 would be a subfeature of Product 1.5 rather than a separate install. Everything went great until we tried to install the complete package on a machine that had both Product 1.0 and Add-On 1.0 installed. Product 1.0 was replaced with 1.5, but although Add-On 1.5 was installed Add-On 1.0 remained on the machine as well. After a couple seconds we had the well duh! moment of realizing that obviously Add-On 1.0 had a different UpgradeCode. We added the second UpgradeCode to the 1.5 installer and everything seemed to be going fine. It uninstalled Product 1.0, but then when it tried to uninstall Add-On 1.0 it logged the following: Action start 14:52:14: ScheduleReboot. DEBUG: Error 2623: Calling ScheduleReboot from a multi-package transaction is not supported. MSI (s) (48:E8) [14:52:21:134]: Product: Add-On -- Internal Error 2623. [...] Action ended 14:52:21: ScheduleReboot. Return value 3. Action ended 14:52:21: INSTALL. Return value 3. and shortly thereafter: Action ended 14:52:21: RemoveExistingProducts. Return value 3. Action ended 14:52:21: INSTALL. Return value 3. and thus complete failure of the entire installation. We're already passing in REBOOT=ReallySuppress to the msi, however that value is not being passed to the old installers by the Upgrade/RemoveExistingProducts action, and a little research seems to indicate there's no way to do so. I did find a blog post from Rob Mensching last year describing how to pass property values using registry keys in such situations, but it seems that would have required us to know about the issue when writing the installers for Product 1.0 and Add-On 1.0, and it's a little late for that now. Luckily we are using our own inhouse bootstrapper so we can use multiple steps to solve this issue in a number of ways. 1: Split it up into two separate installers again, each of which will upgrade one of the old items. This would be simple, but would be moving against the direction we want to take the product in and would perpetuate the problem into the future. 2: Use the old product codes to uninstall them via MSIExec programmatically (using silent mode and REBOOT=ReallySuppress of course) before running the main msi. 3: Create two fake msi's which contain no elements but that that we can run before the real msi to upgrade both products to version 1.0.9. Hopefully that would allow us to upgrade the empty 1.0.9 version to 1.1.0 in the real msi without running into the required reboot problem. Are there any obvious roadblocks to options 2 or 3 that i haven't thought about yet? Or is there some tricky way to get around the ScheduleReboot action in the chained RemoveExistingProducts actions? Thanks! -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Wix 3.6 Bootstrapper Issues
Hi, I have created a bootstrapper (using burn in visual studio 2010) which installs .Net framework4 as prerequisite and then installs the actual msi. Following are the problem that I am facing and I really need your help to resolve those problems. 1 I don't want the bootstrapper to have an entry in Add Remove Program;so I am not using Name attribute in Bundle tag. But as a result of that, my bootstrapper dialog displays only the text Setup. Please let me know is there any way to set the title text without specifying Name attribute in Bundle tag. 2 I am unable to set the icon of bootstrapper dialog. How to do this? 3 The bootstrapper exe is working fine but whenever I try to cancel the installation in midway the bootstrapper crashes. Is that a bug in Win 3.6 or I am doing something wrong? Please help me to resolve these problems. Thanks in advance. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix 3.6 Bootstrapper Issues
Sounds like you are using an old version. Upgrade to latest build for all that to work. On Wed, Apr 25, 2012 at 9:15 PM, Anirban Paul ani.banti.24...@gmail.comwrote: Hi, I have created a bootstrapper (using burn in visual studio 2010) which installs .Net framework4 as prerequisite and then installs the actual msi. Following are the problem that I am facing and I really need your help to resolve those problems. 1 I don't want the bootstrapper to have an entry in Add Remove Program;so I am not using Name attribute in Bundle tag. But as a result of that, my bootstrapper dialog displays only the text Setup. Please let me know is there any way to set the title text without specifying Name attribute in Bundle tag. 2 I am unable to set the icon of bootstrapper dialog. How to do this? 3 The bootstrapper exe is working fine but whenever I try to cancel the installation in midway the bootstrapper crashes. Is that a bug in Win 3.6 or I am doing something wrong? Please help me to resolve these problems. Thanks in advance. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix 3.6 Bootstrapper Issues
Ok I shall try that and get back to you. But let me know the wix variable names that are used to set bootstrapper dialog title and bootstrapper dialog icon. On Thu, Apr 26, 2012 at 10:53 AM, Rob Mensching r...@robmensching.comwrote: Sounds like you are using an old version. Upgrade to latest build for all that to work. On Wed, Apr 25, 2012 at 9:15 PM, Anirban Paul ani.banti.24...@gmail.com wrote: Hi, I have created a bootstrapper (using burn in visual studio 2010) which installs .Net framework4 as prerequisite and then installs the actual msi. Following are the problem that I am facing and I really need your help to resolve those problems. 1 I don't want the bootstrapper to have an entry in Add Remove Program;so I am not using Name attribute in Bundle tag. But as a result of that, my bootstrapper dialog displays only the text Setup. Please let me know is there any way to set the title text without specifying Name attribute in Bundle tag. 2 I am unable to set the icon of bootstrapper dialog. How to do this? 3 The bootstrapper exe is working fine but whenever I try to cancel the installation in midway the bootstrapper crashes. Is that a bug in Win 3.6 or I am doing something wrong? Please help me to resolve these problems. Thanks in advance. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix Burn: Help with silent install (ExePackage
Very hard to tell. It very much depends on how the executable works. Burn just launches the executable and passes the appropriate command-line (InstallCommand for install and UninstallCommand for uninstall and RepairCommand for repair). On Wed, Apr 25, 2012 at 12:18 AM, Miss Parker caisa.westl...@gmail.comwrote: Alright, I tried a different install command according to an example I found in the forum: ExePackage Id=Update SuppressSignatureVerification=yes SourceFile=C:\Downloads\Update_1.12.10.exe PerMachine=yes InstallCommand=/qn UninstallCommand=/qn Vital=no/ It didn't work for me unfortunately. I'm very sorry if I seem a bit slow here, but I don't understand exactly what input InstallCommand needs. I also tried to input the complete msiexec /qn /i command (which works from command line), but no luck. My logfile has this: /Applying execute package: TTUpdate, action: Install, path: C:\Documents and Settings\All Users\Application Data\Package Cache\CC325E7E72D2C044FBEF06359187E9475C1D8D77\Update_1.12.10.exe, arguments: 'C:\Documents and Settings\All Users\Application Data\Package Cache\CC325E7E72D2C044FBEF06359187E9475C1D8D77\Update_1.12.10.exe /qn'/ What am I doing wrong? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Burn-Help-with-silent-install-ExePackage-tp7496163p7498509.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrade a product with add-ons without requiring a reboot?
I wouldn't do 3. It just sounds messy. You could also consider shipping a patch for Add-on 1.0 to fix it. PS: This is why you should always ship an upgrade of your v1 product before you ship v1. smile/ On Wed, Apr 25, 2012 at 5:03 PM, Daetrin Ungashak gfin...@gmail.com wrote: A long time ago our company released a product, let's call it Product 1.0. A little while later we released an add-on, let's call it Add-On 1.0. Now we are releasing Product 1.5. However we decided that for this version Add-On 1.5 would be a subfeature of Product 1.5 rather than a separate install. Everything went great until we tried to install the complete package on a machine that had both Product 1.0 and Add-On 1.0 installed. Product 1.0 was replaced with 1.5, but although Add-On 1.5 was installed Add-On 1.0 remained on the machine as well. After a couple seconds we had the well duh! moment of realizing that obviously Add-On 1.0 had a different UpgradeCode. We added the second UpgradeCode to the 1.5 installer and everything seemed to be going fine. It uninstalled Product 1.0, but then when it tried to uninstall Add-On 1.0 it logged the following: Action start 14:52:14: ScheduleReboot. DEBUG: Error 2623: Calling ScheduleReboot from a multi-package transaction is not supported. MSI (s) (48:E8) [14:52:21:134]: Product: Add-On -- Internal Error 2623. [...] Action ended 14:52:21: ScheduleReboot. Return value 3. Action ended 14:52:21: INSTALL. Return value 3. and shortly thereafter: Action ended 14:52:21: RemoveExistingProducts. Return value 3. Action ended 14:52:21: INSTALL. Return value 3. and thus complete failure of the entire installation. We're already passing in REBOOT=ReallySuppress to the msi, however that value is not being passed to the old installers by the Upgrade/RemoveExistingProducts action, and a little research seems to indicate there's no way to do so. I did find a blog post from Rob Mensching last year describing how to pass property values using registry keys in such situations, but it seems that would have required us to know about the issue when writing the installers for Product 1.0 and Add-On 1.0, and it's a little late for that now. Luckily we are using our own inhouse bootstrapper so we can use multiple steps to solve this issue in a number of ways. 1: Split it up into two separate installers again, each of which will upgrade one of the old items. This would be simple, but would be moving against the direction we want to take the product in and would perpetuate the problem into the future. 2: Use the old product codes to uninstall them via MSIExec programmatically (using silent mode and REBOOT=ReallySuppress of course) before running the main msi. 3: Create two fake msi's which contain no elements but that that we can run before the real msi to upgrade both products to version 1.0.9. Hopefully that would allow us to upgrade the empty 1.0.9 version to 1.1.0 in the real msi without running into the required reboot problem. Are there any obvious roadblocks to options 2 or 3 that i haven't thought about yet? Or is there some tricky way to get around the ScheduleReboot action in the chained RemoveExistingProducts actions? Thanks! -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix Burn: Help with silent install (ExePackage
Yeah well, apparently a simple /s sufficed. I tried that before of course, but probably in combination with something else, which made the silent install fail. Thank you all for your input, I learn more and more about Burn everyday. :) -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Burn-Help-with-silent-install-ExePackage-tp7496163p7501681.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn - MSIPackage InstallCondition evaluates to false, attempts minor upgrade
Sounds like we should scan patches for those that disallow removal and mark them permanent. The InstallCondition behavior is expected. If the InstallCondition is false that means this Package should not be Installed (aka: should not exist on the box). On Wed, Apr 25, 2012 at 9:30 AM, Bob Arnson b...@joyofsetup.com wrote: On 25-Apr-12 10:06, Pally Sandher wrote: Why is it attempting to uninstall the patch when the condition is false the patch has AllowRemoval=no? Because Burn always attempts to uninstall a package that's present when its install condition is false, and Burn doesn't know the patch is permanent. You can file a feature request to change either of those facts or consider using patch applicability instead of install conditions to control the patch installation. -- sig://boB http://joyofsetup.com/ -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Populating Registry Value in TextBox
Instead of using a hard coded Custom/@Sequence number can you use a relative Before/After to ensure the action executes before the UI shows up. Otherwise, look in a verbose log file and see that the Property is getting set correctly before it is used. On Tue, Apr 24, 2012 at 6:39 AM, Ravi Raj raviraj.callin...@gmail.comwrote: Hi, I am trying to populate a registry value in textbox but not being able to do so. Following is my code: Property Id=SDK_MACHINE Secure=yes RegistrySearch Id=sdk_Machine Root=HKCU Key=Software\PATH FOR REGISTRY Name=ValueName Type=raw //Property CustomAction Id=CA_SetProperty_SDK_MACHINE Property=INSTALLMACHINE Value=[SDK_MACHINE] Execute=firstSequence / --- Control Id=NameEdit Type=Edit X=25 Y=105 Width=220 Height=18 Property=INSTALLMACHINE / --- InstallUISequence Custom Action=CA_SetProperty_SDK_MACHINE Sequence=701 / /InstallUISequence -- Thanks and Regards, Ravi Raj -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] -cc CabCache and reusecab settings Bug? or as designed?
I did lots of work was done in WiX v3.6 to get this scenario fixed to work as you describe at the end. What version of the WiX toolset are you using? On Fri, Apr 20, 2012 at 1:56 PM, Abbott, Brian (GE Energy) brian.abb...@ge.com wrote: I'm trying to use wix to build an installer for distributing and setting up an automated test environment. This is really made up of 3 parts, the application code (which is installed via its own installer), the test code which I'm using wix for, and some databases that contain the data used during test. The Databases are where I run into trouble, I was hoping to package them up in my installer I've built for the test code but it takes forever to put them into a cab file, like an hour for the 500Mb of database files. This is really unacceptable to me because I want to use this as part of an automated build process - thus began my search for an optimization. First I found the -cc and -reusecab options and tried them but because the test code files are changing with each compile the cab gets rebuilt. Next I tried using -reusecab but separating out the Database files into a separate cab, still it gets rebuilt. So my question boils down to this: Should -reusecab regenerate 'all' the cab files if any single one of them is out of date, or should it be regenerating only the out of date cab files? Is there a better solution? I think ideally if your wix project generates multiple cab files then -reusecab should check each one individually and only rebuild those that don't match the current files. Brian Abbott Software Quality Engineer -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
