[WiX-users] Can I localize Bundle Name in bootstrapper project?
Hi guys, I meet a problem when create a Wix bootstrapper project. I need to localize the product name shown in the windows system uninstall list. As I know, the name is decided by the Name attribute in Bundle element in Bundle.wxs Here is my bootstrapper project Bundle.wxs ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:util=http://schemas.microsoft.com/wix/UtilExtension; xmlns:bal=http://schemas.microsoft.com/wix/BalExtension; Bundle Name=My Test Application Version=1.0.0.1 Manufacturer=Bryan UpgradeCode=xxx .. /Bundle /Wix How can I change the Name=My Test Application by different culture code? Is there any variable to set this? Thanks for your helps! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Can-I-localize-Bundle-Name-in-bootstrapper-project-tp7592103.html Sent from the wix-users mailing list archive at Nabble.com. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Can I localize Bundle Name in bootstrapper project?
Hi guys, I meet a problem when create a Wix bootstrapper project. I need to localize the product name shown in the windows system uninstall list. As I know, the name is decided by the Name attribute in Bundle element in Bundle.wxs Here is my bootstrapper project Bundle.wxs ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:util=http://schemas.microsoft.com/wix/UtilExtension; xmlns:bal=http://schemas.microsoft.com/wix/BalExtension; Bundle Name=My Test Application Version=1.0.0.1 Manufacturer=Bryan UpgradeCode=xxx .. /Bundle /Wix How can I change the Name=My Test Application by different culture code? Is there any variable to set this? Thanks for your helps! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Can-I-localize-Bundle-Name-in-bootstrapper-project-tp7592104.html Sent from the wix-users mailing list archive at Nabble.com. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] customizing burn prerequisite boostrapper image in theme
Thanks a lot for the useful reply and solution. I was in search of this... Be happy forever.. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/customizing-burn-prerequisite-boostrapper-image-in-theme-tp7205852p7592105.html Sent from the wix-users mailing list archive at Nabble.com. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper
So per users can installer to C:\Program Files\ ? -Original Message- From: Sascha Sertel [mailto:sascha.ser...@gmail.com] Sent: January-24-14 6:45 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper No I did not set ALLUSERS directly. On Fri, Jan 24, 2014 at 2:32 PM, Rob Mensching r...@robmensching.com wrote: Did you have ALLUSERS set the whole time as well? -Original Message- From: Sascha Sertel [mailto:sascha.ser...@gmail.com] Sent: Friday, January 24, 2014 2:21 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper I always had Package/@InstallScope='perUser', that never changed. But the key thing for me to get it to work was MSIINSTALLPERUSER=1, without it I kept getting the insufficient privileges error both in the bundle and when running the stand-alone MSI. // Sascha On Fri, Jan 24, 2014 at 1:34 PM, Rob Mensching r...@robmensching.com wrote: Burn does lots of work to make this scenario work (per-machine prerequisites and one or more per-user packages). It's unique among bootstrappers because it does it in all the right user contexts and all that. I saw a follow up email from you on a fork of this thread that found the most important thing: You need to make sure your per-user package is truly per-user. The easiest way to do that is to use: Package/@InstallScope='perUser'. -Original Message- From: Sascha Sertel [mailto:sascha.ser...@gmail.com] Sent: Friday, January 24, 2014 12:18 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper Let me clarify a bit to tell you what I'm trying to do, what I've tried, and what I thought isn't currently working: Goal: Build a WiX installer for my software which installs .NET Framework 4.5.1 if needed, C++ Runtime if needed, and my software. My software needs to be installed per-user, i.e. it should go into AppData\Local, not Program Files. My understanding is - To accomplish my goal I need three components: .NET Framework 4.5.1 package (provided by NetFx extension), C++ Runtime merge module, and MSI for my software - The two prerequisites needs to be installed on a per-machine (elevated) level, my software on a per-user level This is what I've tried: Attempt 1. Created a WiX bundle with two packages inside the Chain element: A PackageGroupRef for NetFx451Web, and an MsiPackage that includes my software as well as the C++ merge module. Problem: This wouldn't build because my software Package had InstallScope perUser but apparently the C++ merge module forced ALLUSERS=1 which conflicted with the perUser setting. This problem went away when I took the merge module out of the package. Attempt 2: Created a WiX bundle with three packages inside the Chain element: A PackageGroupRef for NetFx451Web, an MsiPackage for my C++ Runtime merge module (InstallScope perMachine), and an MsiPackage for my software (InstallScope perUser). Problem: When running the resulting bundle it would prompt for elevation (which is fine), then install .NET Framework fine, then install the merge module fine, but throw an error for my perUser package: The installer has insufficient privileges to access this directory: C:\Program Files\product. The installation cannot continue. Log on as administrator or contact your system administrator. My software package uses a folder underneath ProgramFilesFolder as the target folder and I was expecting that on Win7 and up in a per-user install it automatically translates to LocalAppDataFolder instead. I thought from what I had gathered in this thread is that once the bundle gets elevated permissions it will also try to run my software package in forced per machine mode but without elevation, and therefore fails when trying to access the Program Files directory. Your last remark sounds though as if this should work. Please help me understand what I'm doing wrong. // Sascha On Fri, Jan 24, 2014 at 11:14 AM, Rob Mensching r...@robmensching.com wrote: If you package is per-user then Burn handles that correctly. It will elevate only if necessary (i.e installing per-machine prerequisites) and install your per-user package. Burn is *designed* to handle that correctly. -Original Message- From: Sascha [mailto:sascha.ser...@gmail.com] Sent: Friday, January 24, 2014 10:51 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper I just ran into this exact same issue and have been trying to find a suitable solution. I need to install the .NET Framework and also a newer C++ runtime as per-machine
Re: [WiX-users] Install busy executables at reboot - Windows 7
Got it!
I haven't worked out all the details but changing the MSIRMSHUTDOWN
property to 0 makes it do what I wanted. Note that in this case the .exe
files that I want to keep running aren't actually being modified. Our
deployment folks just don't like to deal with distribution of patches;
they'd rather send out a full MSI.
Here are the properties I have set, in case some future reader comes upon
this thread. I think it's only the last three that matter but I haven't dug
through all of the Reinstall... ones.
Property Id=REBOOT Admin=yes Secure=yesReallySuppress/Property
Property Id=ARPNOMODIFY Value=1 /
Property Id=ARPNOREPAIR Value=1 /
Property Id=DISABLEROLLBACK Value=1 /
Property Id=ReinstallFileOlderVersion Value=o /
Property Id=ReinstallFileVersion Value=o /
Property Id=ReinstallRepair Value=r /
* Property Id=MSIRESTARTMANAGERCONTROL Value=0 / *
* Property Id=MSIRMSHUTDOWN Value=2 / *
* Property Id=MSIDISABLERMRESTART Value=0 /*
On Sun, Jan 26, 2014 at 7:00 AM, Walter Dexter wfdex...@gmail.com wrote:
I tried that. Disable just makes it use the older method instead of the
restart manager. In practical terms, it's just a different dialog box if
you don't use the /quiet option, and no difference in behavior if you do.
I'm going to try actually having the restart manager restart them and see
how disruptive that is,but it wouldn't surprise me if the default quiet
behavior is to not restart.
On Jan 25, 2014 12:42 PM, Rob Mensching r...@robmensching.com wrote:
Maybe MSIRESTARTMANAGERCONTROL is the one that would actually help. Your
example shows a 0. You might use Disable. Ultimately, all this is
documented here:
http://msdn.microsoft.com/en-us/library/aa372059(v=vs.85).aspx
-Original Message-
From: Walter Dexter [mailto:wfdex...@gmail.com]
Sent: Saturday, January 25, 2014 9:12 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Install busy executables at reboot - Windows 7
I tried MSIRMSHUTDOWN = 2, and REBOOT is = ReallySuppress. Behavior is
the same - with /quiet it just quietly kills the exe off, without /quiet it
asks me what to do (the Reinstall Manager prompt.)
I hate to drop a giant XML bomb on the forum, but here's a (trimmed down,
believe it or not) WXS file.
If you (Rob) or anyone has some advice, I sure appreciate it. Otherwise I
guess I'll just do the console logoff as a custom action and take some more
time to figure it out.
Walt
?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:util=
http://schemas.microsoft.com/wix/UtilExtension;
?define ProductName=MCO e*System Integration Files ?
?define UpgradeCode={B44477EF-7487-4302-875C-DA2846EB30DA} ?
?define ProductVersion=1.0.5.0 ? !-- Product version. --
?define MaxVersion=1.0.5.0 ? !-- Highest version this should upgrade.
Most of the time, should be same as ProductVersion.--
?define MinVersion=1.0.0.0 ? !-- Lowest version this should upgrade.
--
Product
Id=*
Name=$(var.ProductName)
Language=1033
Version=$(var.ProductVersion)
Manufacturer=Our Co, LLC
UpgradeCode=$(var.UpgradeCode)
Package
InstallerVersion=300
Compressed=yes
InstallScope=perMachine
Comments=No detail.
Description=e*System Integration Programs
Manufacturer=US e*System Integration - Walt Dexter -
walter.dex...@example.com /
Upgrade Id=$(var.UpgradeCode)
UpgradeVersion
IgnoreRemoveFailure=yes
IncludeMinimum=yes
IncludeMaximum=yes
Minimum=$(var.MinVersion)
Maximum=$(var.MaxVersion)
MigrateFeatures=yes
Property=UPGRADE_1
/UpgradeVersion
/Upgrade
MediaTemplate EmbedCab=yes CompressionLevel=high /
Feature Id=FEAT_ALLFILES Title=e*System Integration Files Level=1
ComponentGroupRef Id=CMPG_SCRIPTS /
/Feature
Property Id=REBOOT Admin=yes Secure=yesReallySuppress/Property
Property Id=ARPCOMMENTSe*System Application from
Metametrics/Property
Property Id=ARPCONTACTUS e*Restaurant Integration - Walt
Dexter/Property
Property Id=ARPNOMODIFY Value=1 /
Property Id=ARPNOREPAIR Value=1 /
Property Id=DISABLEROLLBACK Value=1 /
!-- Property Id=REINSTALLMODE Value=amus / --
Property Id=MSIRESTARTMANAGERCONTROL Value=0 /
Property Id=MSIRMSHUTDOWN Value=2 /
Property Id=ReinstallFileOlderVersion Value=o /
Property Id=ReinstallFileVersion Value=o /
Property Id=ReinstallRepair Value=r /
Property Id=MCO___APP_TYPE Value=$(var.ProductName) /
CustomAction Id=CA_SetCDrive Directory=C_DRIVE Value=c:\ /
InstallExecuteSequence
RemoveExistingProducts After=InstallInitialize /
Custom Action=CA_SetCDrive After=CostFinalize /
/InstallExecuteSequence
Directory Id=TARGETDIR Name=SourceDir
Directory Id=C_DRIVE Name=CDrive
Directory Id=DIR_PROGRAMDATA Name=ProgramData
Directory Id=DIR_MICROSOFT Name=Microsoft
Directory Id=DIR_POINTOFSERVICE Name=Point of Service
Directory Id=DIR_CONFIGURATION Name=Configuration /
/Directory
[WiX-users] [SPAM] Re: Making a symbolic link in an installer
The privilege SE_CREATE_SYMBOLIC_LINK_NAME is required. http://msdn.microsoft.com/en-us/library/windows/desktop/aa363866(v=vs.85).aspx The following link has some ideas on how to grant the privledge and I think there are some other approaches which could be implemented in a CA with win32 calls, but I have not tried it. http://stackoverflow.com/questions/815472/how-do-i-grant-secreatesymboliclink-on-windows-vista-home-edition -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Making-a-symbolic-link-in-an-installer-tp7592068p7592108.html Sent from the wix-users mailing list archive at Nabble.com. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Confused... when installing a 32/64 bit MSI using 1 product.wxs file [P]
Blair/Rob
is this statement correct:
So are you saying I should use:
?if $(sys.BUILDARCH) = x64 ? and NOT ?if $(var.Platform) = x64 ?
What about my wixlib where I have 2 files that have a 32 bit version and a
64 bit version what is the proper way to say
32 bit file install on a 32 bit OS and 64 bit file install on a 64 bit OS
AND 32 bit file can be installed on 64 bit OS since the x86 MSI can be
installed on 64bit OS?
Component Id=quot;cmp_Dllquot; Guid=quot;{lt;Some GUID}
File Id=file_Dll KeyPath=yes
Source=$(var.SourcePath)\lib\x86\SomeFile.dll /
Condition
! [ CDATA [$(sys.BUILDARCH) = x64 AND $(sys.BUILDARCH) =
x86] ]
/Condition
/Component
Component Id=quot;cmp_DLLl_x64quot; Guid=quot;{lt;Some
GUID} Win64=$(var.Win)
File Id=file_Dll_x64 KeyPath=yes
Source=$(var.SourcePath)\lib\x64\SomeFile.dll /
Condition
! [CDATA [$(sys.BUILDARCH) = x64] ]
/Condition
/Component
Thanks
Steve
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Re-Confused-when-installing-a-32-64-bit-MSI-using-1-product-wxs-file-P-tp7591967p7592109.html
Sent from the wix-users mailing list archive at Nabble.com.
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] 'http://schemas.microsoft.com/wix/UtilExtension'
Any idea how to get around the reference error to UtilExtension? Or, is there a new/different way of setting a service failure action? The ServiceInstall element contains an unhandled extension element 'util:ServiceConfig'. Please ensure that the extension for elements in the 'http://schemas.microsoft.com/wix/UtilExtension' namespace has been provided. Wix xmlns= http://schemas.microsoft.com/wix/2006/wi xmlns:util= http://schemas.microsoft.com/wix/UtilExtension ServiceInstall Id=ServiceInstaller Type=ownProcess Vital=yes Name=TourRunService DisplayName=MyName Description=MyDescription. Start=auto Account=LocalSystem ErrorControl=normal ServiceDependency Id=ActivityLogWcfServiceHost/ util:ServiceConfig ServiceName=TourRunService FirstFailureActionType=restart SecondFailureActionType=restart ThirdFailureActionType=restart RestartServiceDelayInSeconds=60 ResetPeriodInDays=1/ /ServiceInstall -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: Can I localize Bundle Name in bootstrapper project?
http://wixtoolset.org/documentation/manual/v3/howtos/ui_and_localization/make_installer_localizable.html In the above link (or in your chm file) there is an example of localizing the Name attribute. (It happens to be in a MSI Product element but also could be implemented in a Bundle element.) -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Can-I-localize-Bundle-Name-in-bootstrapper-project-tp7592104p7592106.html Sent from the wix-users mailing list archive at Nabble.com. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] 'http://schemas.microsoft.com/wix/UtilExtension'
Try this Format: ServiceInstall Id=WhateverServiceInstall Name=WhateverService DisplayName=WhateverService Type=ownProcess Start=auto ErrorControl=normal Description=WhateverService Service Vital=yes PermissionEx xmlns=http://schemas.microsoft.com/wix/UtilExtension; User=Administrator ServiceChangeConfig=yes ServiceEnumerateDependents=yes ChangePermission=yes ServiceInterrogate=yes ServicePauseContinue=yes ServiceQueryConfig=yes ServiceQueryStatus=yes ServiceStart=yes ServiceStop=yes / ServiceConfig xmlns=http://schemas.microsoft.com/wix/UtilExtension; RebootMessage =Problem with Service requires a reboot ResetPeriodInDays=3 RestartServiceDelayInSeconds=5 FirstFailureActionType=restart SecondFailureActionType=restart ThirdFailureActionType=reboot/ ServiceDependency Id=MSSQLServer/ /ServiceInstall ServiceControl Id=WhateverServiceServiceInstaller Name=WhateverService Start=install Stop=both Remove=uninstall Wait=no / Quoting jpalmer1...@comcast.net: Any idea how to get around the reference error to UtilExtension? Or, is there a new/different way of setting a service failure action? snip -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Create a new custom step for a WixUI_Advanced installer
Hi, I’m evaluating Wix and I hope someone can give me some clarification on a question I have. I have an installer configured using WixUI_Advanced but I want to extend it by adding a new step to the middle of the setup process. The idea is to have a new screen with two buttons, one of them invoking some custom C# code and the other for moving to the next workflow process. Is this possible to implement? I read about custom actions, I also saw we can build our own setup screens, but I’m not sure if I can do this and hook it up to the WixUI_Advanced setup template. Any ideas? Thank you in advance, Gustavo Sent from Windows Mail -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper
No. That's a per-machine location. -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: Monday, January 27, 2014 7:54 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper So per users can installer to C:\Program Files\ ? -Original Message- From: Sascha Sertel [mailto:sascha.ser...@gmail.com] Sent: January-24-14 6:45 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper No I did not set ALLUSERS directly. On Fri, Jan 24, 2014 at 2:32 PM, Rob Mensching r...@robmensching.com wrote: Did you have ALLUSERS set the whole time as well? -Original Message- From: Sascha Sertel [mailto:sascha.ser...@gmail.com] Sent: Friday, January 24, 2014 2:21 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper I always had Package/@InstallScope='perUser', that never changed. But the key thing for me to get it to work was MSIINSTALLPERUSER=1, without it I kept getting the insufficient privileges error both in the bundle and when running the stand-alone MSI. // Sascha On Fri, Jan 24, 2014 at 1:34 PM, Rob Mensching r...@robmensching.com wrote: Burn does lots of work to make this scenario work (per-machine prerequisites and one or more per-user packages). It's unique among bootstrappers because it does it in all the right user contexts and all that. I saw a follow up email from you on a fork of this thread that found the most important thing: You need to make sure your per-user package is truly per-user. The easiest way to do that is to use: Package/@InstallScope='perUser'. -Original Message- From: Sascha Sertel [mailto:sascha.ser...@gmail.com] Sent: Friday, January 24, 2014 12:18 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper Let me clarify a bit to tell you what I'm trying to do, what I've tried, and what I thought isn't currently working: Goal: Build a WiX installer for my software which installs .NET Framework 4.5.1 if needed, C++ Runtime if needed, and my software. My software needs to be installed per-user, i.e. it should go into AppData\Local, not Program Files. My understanding is - To accomplish my goal I need three components: .NET Framework 4.5.1 package (provided by NetFx extension), C++ Runtime merge module, and MSI for my software - The two prerequisites needs to be installed on a per-machine (elevated) level, my software on a per-user level This is what I've tried: Attempt 1. Created a WiX bundle with two packages inside the Chain element: A PackageGroupRef for NetFx451Web, and an MsiPackage that includes my software as well as the C++ merge module. Problem: This wouldn't build because my software Package had InstallScope perUser but apparently the C++ merge module forced ALLUSERS=1 which conflicted with the perUser setting. This problem went away when I took the merge module out of the package. Attempt 2: Created a WiX bundle with three packages inside the Chain element: A PackageGroupRef for NetFx451Web, an MsiPackage for my C++ Runtime merge module (InstallScope perMachine), and an MsiPackage for my software (InstallScope perUser). Problem: When running the resulting bundle it would prompt for elevation (which is fine), then install .NET Framework fine, then install the merge module fine, but throw an error for my perUser package: The installer has insufficient privileges to access this directory: C:\Program Files\product. The installation cannot continue. Log on as administrator or contact your system administrator. My software package uses a folder underneath ProgramFilesFolder as the target folder and I was expecting that on Win7 and up in a per-user install it automatically translates to LocalAppDataFolder instead. I thought from what I had gathered in this thread is that once the bundle gets elevated permissions it will also try to run my software package in forced per machine mode but without elevation, and therefore fails when trying to access the Program Files directory. Your last remark sounds though as if this should work. Please help me understand what I'm doing wrong. // Sascha On Fri, Jan 24, 2014 at 11:14 AM, Rob Mensching r...@robmensching.com wrote: If you package is per-user then Burn handles that correctly. It will elevate only if necessary (i.e installing per-machine prerequisites) and install your per-user package. Burn is *designed* to handle that correctly. -Original Message- From: Sascha [mailto:sascha.ser...@gmail.com] Sent: Friday, January 24, 2014 10:51 AM To: wix-users@lists.sourceforge.net
[WiX-users] Best Practice Service verification and installation
Hello All, I can do what I need to do using a custom action, but I am hesitating on that route wandering if WIX has a built in mechanism for this. Here is my situation: On server 2008 I want to verify if the SSDP (Windows Service already installer by the OS, not my own) is installed and ready to start or already started or simply disabled. The service by default on S2008 is disabled, I also want to Popup a message to the user giving him the choice to enable and start this Windows service for the application to work, if he says NO to abort the installation. From what I read in the documentation these calls looked promising but dont seem to do what I need à ServiceConfig and ServiceConfigFailureActions Also ServiceControl wont work since this is used for a service being installed from my installation. So the question is can I do this using WIX elements or is the CustomAction route the best way to go? If I can do this using Wix elements what should I be looking at/for. Thanks for the advice Marc -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] 'http://schemas.microsoft.com/wix/UtilExtension'
If you're talking about this error from candle, or a similar one from light: error CNDL0200 : The Component element contains an unhandled extension element 'Util:blahblahblah'. Please ensure that the extension for elements in the 'http://schemas.microsoft.com/wix/UtilExtension' namespace has been provided. I just hit and resolved this (about an hour ago) by adding the following to both candle and light command lines: -ext c:\Program Files (x86)\WiX Toolset v3.7\bin\WixUtilExtension.dll Obviously your path may vary. On Mon, Jan 27, 2014 at 10:25 AM, Carter Young ecyo...@grandecom.netwrote: Try this Format: ServiceInstall Id=WhateverServiceInstall Name=WhateverService DisplayName=WhateverService Type=ownProcess Start=auto ErrorControl=normal Description=WhateverService Service Vital=yes PermissionEx xmlns=http://schemas.microsoft.com/wix/UtilExtension; User=Administrator ServiceChangeConfig=yes ServiceEnumerateDependents=yes ChangePermission=yes ServiceInterrogate=yes ServicePauseContinue=yes ServiceQueryConfig=yes ServiceQueryStatus=yes ServiceStart=yes ServiceStop=yes / ServiceConfig xmlns=http://schemas.microsoft.com/wix/UtilExtension; RebootMessage =Problem with Service requires a reboot ResetPeriodInDays=3 RestartServiceDelayInSeconds=5 FirstFailureActionType=restart SecondFailureActionType=restart ThirdFailureActionType=reboot/ ServiceDependency Id=MSSQLServer/ /ServiceInstall ServiceControl Id=WhateverServiceServiceInstaller Name=WhateverService Start=install Stop=both Remove=uninstall Wait=no / Quoting jpalmer1...@comcast.net: Any idea how to get around the reference error to UtilExtension? Or, is there a new/different way of setting a service failure action? snip -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: Wix Burn 3.7 .NET 4.5
I am trapped in a similar issue. My custom bootstrapper is based on Net 4.0. As a prereq I want to install Net 4.5 which does work, but since my app itself uses Net 4.0 I ran into the restart-issue which is not usable for me. If I got you right, Nicholas, setting my bootstrapper to 4.5 should force the installer to install the needed .Net right before starting the bootstrapper itself? So no restarting or closing of my installer needed? Torben Nicholas Pierce wrote The pre-requisite bootstrapper seems to only kick in if your application fails to load, so if your MBA actually needed .NET 4.5 it would fail to load with just .NET 4.0 installed at which point the pre-requisite bootstrapper kicks in. Nicholas On 11 January 2013 13:40, Thomas Hammond lt; Thomas.Hammond@ gt; wrote: Yes, it looks like it would actually do that. However, what if my bootstrapper application actually needed .NET 4.5? Would it install it as a prereq, or would by bootstrapper just fail to load? Also, I am really curious why it just doesn't behave the same way it would if .NET 4.0 isn't installed. The detect condition is false, so it seems like there is something strange going on in there. -Thom -Original Message- From: Nicholas Pierce [mailto: nicholas.pierce@ ] Sent: Friday, January 11, 2013 4:31 AM To: wix-users@.sourceforge Subject: Re: [WiX-users] Wix Burn 3.7 .NET 4.5 Does Burn not just install .NET 4.5 in your bootstrapper's main apply phase along with everything else? If you put it first in your chain, it should get installed first by Burn. Nicholas On 10 January 2013 21:19, Thomas Hammond lt; Thomas.Hammond@ gt; wrote: I updated my bundle to use .NET 4.5 as the Mba Prereq. This works fine if I install on a machine that does not have .NET 4.x installed. However, if I run on a system that already has 4.0 installed, Burn does not install .NET 4.5 as a prereq before loading my managed bootstrapper application. Even though my managed bootstrapper application only requires .NET 4.0, I would like to use the prereq system to get .NET 4.5 installed because all of my MSI packages require .NET 4.5. Thanks. -Thom -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_122712 ___ WiX-users mailing list WiX-users@.sourceforge https://lists.sourceforge.net/lists/listinfo/wix-users -- Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 ___ WiX-users mailing list WiX-users@.sourceforge https://lists.sourceforge.net/lists/listinfo/wix-users -- Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 ___ WiX-users mailing list WiX-users@.sourceforge https://lists.sourceforge.net/lists/listinfo/wix-users -- Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 ___ WiX-users mailing list WiX-users@.sourceforge https://lists.sourceforge.net/lists/listinfo/wix-users Nicholas Pierce wrote The pre-requisite bootstrapper seems to only kick in if your application fails to load, so if your MBA actually needed .NET 4.5 it would fail to load with just .NET 4.0 installed at which point the pre-requisite bootstrapper kicks in. Nicholas On 11 January 2013 13:40, Thomas Hammond lt; Thomas.Hammond@ gt; wrote: Yes, it looks like it would actually do that. However, what if my bootstrapper application actually needed .NET 4.5? Would it install it as a prereq, or would by bootstrapper just fail to load? Also, I am really curious why it just doesn't behave the same way it would if .NET 4.0
Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper
With MSIINSTALLPERUSER=1 on Windows 7 and above the ProgramFilesFolder location gets automatically rerouted to LocalAppDataFolder if running a per-User install. This MSDN article shows where all the folder locations point to in per-machine vs. per-user installs: http://msdn.microsoft.com/en-us/library/windows/desktop/dd765197(v=vs.85).aspx // Sascha On Mon, Jan 27, 2014 at 8:46 AM, Rob Mensching r...@robmensching.com wrote: No. That's a per-machine location. -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: Monday, January 27, 2014 7:54 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper So per users can installer to C:\Program Files\ ? -Original Message- From: Sascha Sertel [mailto:sascha.ser...@gmail.com] Sent: January-24-14 6:45 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper No I did not set ALLUSERS directly. On Fri, Jan 24, 2014 at 2:32 PM, Rob Mensching r...@robmensching.com wrote: Did you have ALLUSERS set the whole time as well? -Original Message- From: Sascha Sertel [mailto:sascha.ser...@gmail.com] Sent: Friday, January 24, 2014 2:21 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper I always had Package/@InstallScope='perUser', that never changed. But the key thing for me to get it to work was MSIINSTALLPERUSER=1, without it I kept getting the insufficient privileges error both in the bundle and when running the stand-alone MSI. // Sascha On Fri, Jan 24, 2014 at 1:34 PM, Rob Mensching r...@robmensching.com wrote: Burn does lots of work to make this scenario work (per-machine prerequisites and one or more per-user packages). It's unique among bootstrappers because it does it in all the right user contexts and all that. I saw a follow up email from you on a fork of this thread that found the most important thing: You need to make sure your per-user package is truly per-user. The easiest way to do that is to use: Package/@InstallScope='perUser'. -Original Message- From: Sascha Sertel [mailto:sascha.ser...@gmail.com] Sent: Friday, January 24, 2014 12:18 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] dual-purpose installer (ALLUSERS=2) and Bootstrapper Let me clarify a bit to tell you what I'm trying to do, what I've tried, and what I thought isn't currently working: Goal: Build a WiX installer for my software which installs .NET Framework 4.5.1 if needed, C++ Runtime if needed, and my software. My software needs to be installed per-user, i.e. it should go into AppData\Local, not Program Files. My understanding is - To accomplish my goal I need three components: .NET Framework 4.5.1 package (provided by NetFx extension), C++ Runtime merge module, and MSI for my software - The two prerequisites needs to be installed on a per-machine (elevated) level, my software on a per-user level This is what I've tried: Attempt 1. Created a WiX bundle with two packages inside the Chain element: A PackageGroupRef for NetFx451Web, and an MsiPackage that includes my software as well as the C++ merge module. Problem: This wouldn't build because my software Package had InstallScope perUser but apparently the C++ merge module forced ALLUSERS=1 which conflicted with the perUser setting. This problem went away when I took the merge module out of the package. Attempt 2: Created a WiX bundle with three packages inside the Chain element: A PackageGroupRef for NetFx451Web, an MsiPackage for my C++ Runtime merge module (InstallScope perMachine), and an MsiPackage for my software (InstallScope perUser). Problem: When running the resulting bundle it would prompt for elevation (which is fine), then install .NET Framework fine, then install the merge module fine, but throw an error for my perUser package: The installer has insufficient privileges to access this directory: C:\Program Files\product. The installation cannot continue. Log on as administrator or contact your system administrator. My software package uses a folder underneath ProgramFilesFolder as the target folder and I was expecting that on Win7 and up in a per-user install it automatically translates to LocalAppDataFolder instead. I thought from what I had gathered in this thread is that once the bundle gets elevated permissions it will also try to run my software package in forced per machine mode but without elevation, and therefore fails when trying to access the Program Files directory. Your last remark sounds though as if this should work. Please help me understand what I'm doing wrong.
[WiX-users] finding out what features are being installed
To learn what features are being installed I try to examine ADDLOCAL which is a standard parameter that can be passed to MSI. I use the following line in my WiX xml to do that: SetProperty Id=FEATURELIST Value=[ADDLOCAL] After=CostFinalize/ Then, inside InstallExecuteSequence element I am scheduling custom action which uses my local FEATURELIST property. When I launch the installation with UI (although I have no dialogs), the FEATURELIST holds names of all features separated by comma. When I launch silent installation (i.e. use /qn switch) the value of FEATURELIST is blank. In both cases I do not specify ADDLOCAL, which instructs MSI to install all available features. Why these 2 cases yield different values? I'd always expect the same behavior regardless of /qn switch. If that is not the right way, can somebody please suggest a reliable way of checking what features are being installed ? Thank you -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Best practice for setting x86/x64 for MSI's and installing files...
Hi, I didn't get much traction on my question or at least my last question... ALL of my MSI use this format in a variable.wxi files I have: ?if $(var.Platform) = x64 ? ?define Win64=yes ? ?define PlatformProductName = $(var.ProductName) (64 bit) ? ?define PlatformProgramFilesFolder = ProgramFiles64Folder ? ?define PlatformCAQuietExecDLLEntry = CAQuietExec64? ?define PlatformQtExecCmdLine = QtExec64CmdLine? ?else ? ?define Win64=no ? ?define PlatformProductName = $(var.ProductName) ? ?define PlatformProgramFilesFolder = ProgramFilesFolder ? ?define PlatformCAQuietExecDLLEntry = CAQuietExec? ?define PlatformQtExecCmdLine = QtExecCmdLine? ?endif ? Should I use: ?if $(sys.BUILDARCH) = x64 ? and NOT ?if $(var.Platform) = x64 ? ?? What about my wixlib where I have 2 files that have a 32 bit version and a 64 bit version what is the proper way to say 32 bit file install on a 32 bit OS and 64 bit file install on a 64 bit OS AND 32 bit file can be installed on 64 bit OS since the x86 MSI can be installed on 64bit OS? Component Id=cmp_SQLite.Interop_x86 Guid=SOME GUID File Id=file_SQLite.Interop_x86 KeyPath=yes Source=$(var.sourcePath)ThirdParty\SQLite\x86\SQLite.Interop.dll / Condition ! [ CDATA [NOT(VersionNT64) OR $(var.Platform) = x86] ] /Condition /Component Component Id=cmp_SQLite.Interop_x64 Guid=SOME GUID File Id=file_SQLite.Interop_x64 KeyPath=yes Source=$(var.sourcePath)ThirdParty\SQLite\x64\SQLite.Interop.dll / Condition ! [ CDATA [VersionNT64 OR $(var.Platform) = x64] ] /Condition /Component thanks, Steve ps I have put some spaces in the Condition since the nabble message format strips out the data -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Best-practice-for-setting-x86-x64-for-MSI-s-and-installing-files-tp7592126.html Sent from the wix-users mailing list archive at Nabble.com. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] !(loc.XXX) or #(loc.XXX)
In WIX, localization strings are referenced using the !(loc.xxx) syntax, and defined in WXL files: http://wixtoolset.org/documentation/manual/v3/howtos/ui_and_localization/make_installer_localizable.html However, I find to enable localization strings in a bundle using WIX standard bootstrapper application, it uses a different syntax: #(loc.xxx) http://wixtoolset.org/documentation/manual/v3/bundle/wixstdba/wixstdba_customize.html 1. Why do we introduce such inconsistency? 2. From the WIX source code, WixVariableResolver.ResolveVariables(), it seems to only support !(loc.xxx) or $(loc.xxx) which will message out a warning WixWarnings.DeprecatedLocalizationVariablePrefix. If this is the case, wixstdba seems to either implement the localization on its own, or replace '#' with '!' before feeding to WixVariableResolver? Thanks, Jun -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Install busy executables at reboot - Windows 7
2014-01-27 Walter Dexter wfdex...@gmail.com: Got it! I haven't worked out all the details but changing the MSIRMSHUTDOWN property to 0 makes it do what I wanted. Note that in this case the .exe files that I want to keep running aren't actually being modified. Our deployment folks just don't like to deal with distribution of patches; they'd rather send out a full MSI. Windows Installer only overwrites files that have changed; patch or no patch is irrelevant. -- Nicolás -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] !(loc.XXX) or #(loc.XXX)
1. $() are resolved and preprocessing, !() are resolved and binding, and #() is resolved at runtime. 2. The latter. -Original Message- From: Jun Yin [mailto:jun...@microsoft.com] Sent: Monday, January 27, 2014 5:04 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] !(loc.XXX) or #(loc.XXX) In WIX, localization strings are referenced using the !(loc.xxx) syntax, and defined in WXL files: http://wixtoolset.org/documentation/manual/v3/howtos/ui_and_localization/make_installer_localizable.html However, I find to enable localization strings in a bundle using WIX standard bootstrapper application, it uses a different syntax: #(loc.xxx) http://wixtoolset.org/documentation/manual/v3/bundle/wixstdba/wixstdba_customize.html 1. Why do we introduce such inconsistency? 2. From the WIX source code, WixVariableResolver.ResolveVariables(), it seems to only support !(loc.xxx) or $(loc.xxx) which will message out a warning WixWarnings.DeprecatedLocalizationVariablePrefix. If this is the case, wixstdba seems to either implement the localization on its own, or replace '#' with '!' before feeding to WixVariableResolver? Thanks, Jun -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Best practice for setting x86/x64 for MSI's and installing files...
I believe Condition element only needs VersionNT64 to differentiate at runtime. In 32-bit build, reference only Id_x86. In 64-bit build, reference both Id_x86 and Id_x64. -Original Message- From: StevenOgilvie [mailto:sogil...@msn.com] Sent: Monday, January 27, 2014 3:00 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Best practice for setting x86/x64 for MSI's and installing files... Hi, I didn't get much traction on my question or at least my last question... ALL of my MSI use this format in a variable.wxi files I have: ?if $(var.Platform) = x64 ? ?define Win64=yes ? ?define PlatformProductName = $(var.ProductName) (64 bit) ? ?define PlatformProgramFilesFolder = ProgramFiles64Folder ? ?define PlatformCAQuietExecDLLEntry = CAQuietExec64? ?define PlatformQtExecCmdLine = QtExec64CmdLine? ?else ? ?define Win64=no ? ?define PlatformProductName = $(var.ProductName) ? ?define PlatformProgramFilesFolder = ProgramFilesFolder ? ?define PlatformCAQuietExecDLLEntry = CAQuietExec? ?define PlatformQtExecCmdLine = QtExecCmdLine? ?endif ? Should I use: ?if $(sys.BUILDARCH) = x64 ? and NOT ?if $(var.Platform) = x64 ? ?? What about my wixlib where I have 2 files that have a 32 bit version and a 64 bit version what is the proper way to say 32 bit file install on a 32 bit OS and 64 bit file install on a 64 bit OS AND 32 bit file can be installed on 64 bit OS since the x86 MSI can be installed on 64bit OS? Component Id=cmp_SQLite.Interop_x86 Guid=SOME GUID File Id=file_SQLite.Interop_x86 KeyPath=yes Source=$(var.sourcePath)ThirdParty\SQLite\x86\SQLite.Interop.dll / Condition ! [ CDATA [NOT(VersionNT64) OR $(var.Platform) = x86] ] /Condition /Component Component Id=cmp_SQLite.Interop_x64 Guid=SOME GUID File Id=file_SQLite.Interop_x64 KeyPath=yes Source=$(var.sourcePath)ThirdParty\SQLite\x64\SQLite.Interop.dll / Condition ! [ CDATA [VersionNT64 OR $(var.Platform) = x64] ] /Condition /Component thanks, Steve ps I have put some spaces in the Condition since the nabble message format strips out the data -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Best-practice-for-setting-x86-x64-for-MSI-s-and-installing-files-tp7592126.html Sent from the wix-users mailing list archive at Nabble.com. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Install busy executables at reboot - Windows 7
I believe that is only true for versioned files, although I may be mistaken. In this particular case (properly versioned .Net 3.5 executables) they were unchanged and should not have been replaced according to my, and your, understanding of the rules. Despite that, Windows Installer was killing them off. Perhaps it just shoots first and asks questions later unless told to not terminate. I have no idea. On Mon, Jan 27, 2014 at 7:17 PM, Nicolás Alvarez nicolas.alva...@gmail.comwrote: 2014-01-27 Walter Dexter wfdex...@gmail.com: Got it! I haven't worked out all the details but changing the MSIRMSHUTDOWN property to 0 makes it do what I wanted. Note that in this case the .exe files that I want to keep running aren't actually being modified. Our deployment folks just don't like to deal with distribution of patches; they'd rather send out a full MSI. Windows Installer only overwrites files that have changed; patch or no patch is irrelevant. -- Nicolás -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] VB6 OCX And Harvest
Personally I think it should have been implemented that way but it wasn’t. Blair From: Graham Allwood Sent: Thursday, January 23, 2014 10:34 PM To: General discussion for Windows Installer XML toolset. Thanks Blair. That did the trick. I was trying to use AdditionalOptions element in the HarvestFile command/element but this didn't work. Graham -Original Message- From: Blair Murri [mailto:os...@live.com] Sent: 24 January 2014 06:04 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VB6 OCX And Harvest Add HarvestFileAdditionalOptions-svb6/HarvestFileAdditionalOptions to the first PropertyGroup in your WIXPROJ. Blair From: Graham Allwood Sent: Wednesday, January 22, 2014 11:45 PM To: General discussion for Windows Installer XML toolset. Hi, I have three VB6 components in a VB6 project I want to install and register. Two are ocx's and one is a dll. I see in the SDK Docs there is a -svb6 option for Harvest which I think I need to use. Is this right? I am actually using MSBUILD and the Harvestfile element. There doesn't seem to be a property for the above option. Does anyone know how to use HarvestFile with a VB6 COM dll? Thanks for your help Graham Allwood -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Setup.exe cygwin question
Certainly it is possible using a custom BA from a bundle. Somewhat less so from an MSI. One big advantage of the bundle, however, is that the entire set of packages can be divided up between some arbitrary set of MSIs abstracted away from the end user (in fact, the most logical would be to have each package be an MSI). In fact, you might even be able to reuse your current UI in a custom bundle and save much of the redevelopment effort. Not sure on the project leader part. What resources are available to such a leader (types and experience of developers/testers/PMs, etc.)? Blair From: BGINFO4X Sent: Friday, January 24, 2014 7:25 AM To: General discussion for Windows Installer XML toolset. Dear Sirs. Attending your experience, do you think that is possible to build an installer like the traditional setup.exe installer from cygwin.com? In the following url you can see the main screens. http://x.cygwin.com/docs/ug/setup-cygwin-x-installing.html I ask basically for the screens number 11, 13, 15, 16. Do you think that this is possible with WIX? Does anyone would like to be the project leader of such project? cygwin community should agree with this. I must admit that I can't build such project, I don't have the necessary experience and knowledge. Any recommendation is welcome. Thanks for your time and regards. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] searching for a registry key without worrying about any values
You always control the registry key? Do it like the property remember pattern. Blair From: Sean Farrow Sent: Friday, January 24, 2014 8:23 AM To: General discussion for Windows Installer XML toolset. Hi all, I'm in the process of refactoring an installer I wrote a while ago. I've got a situation where I need to check that a registry key exists (I'm not worried about any of the values). What is the best way of doing this and assigning it to a property? I thought about setting the property to an initial value say test, and as the default value is an empty string I could check to see whether the string is empty and hence the property has been set. Or, Will the Util extension help here? How can I set a variable value to a property? I'm currently using a custom action to do this using RegOpenKey internally. Any help appreciated. Cheers Sean. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Enabling platform features during install
from: http://msdn.microsoft.com/library/windows/desktop/hh825838.aspx “You can develop applications by using the DISM API on any computer where you have installed the Windows® Assessment and Deployment Kit (Windows ADK).” So, I interpret that as saying that you can’t statically link the DISM API and use it during an installation (unless you effectively make the ADK a prerequisite). That nixes it for my use cases. Blair From: Phill Hogland Sent: Friday, January 24, 2014 8:49 AM To: General discussion for Windows Installer XML toolset. I do not have the ADK or the path either. And the API docs talk about creating a 'application' which will modify /online images. Here is a sample: http://msdn.microsoft.com/en-us/library/windows/desktop/hh824804.aspx I am preparing a CA to test pieces of this code relating to the query of a feature status, as a test of the concept. I am not quite ready to try and compile it without or with the ADK, but I hope to have a better idea later today after I work on some other issues. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Enabling-platform-features-during-install-tp7591862p7592047.html Sent from the wix-users mailing list archive at Nabble.com. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
