Re: [WiX-users] Localizing Burn Condition messages
It does work. Just had to use the *#*(loc.StringId) instead of the *!*(loc.StringId) syntax for the bal:Condition@Message attribute. The WixStdBA localizes with the # syntax. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Localizing-Burn-Condition-messages-tp7600408p7600468.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Localizing Burn Condition messages
I am using the WixStdBA and have got it (mostly) localized by following the 'Payload Name=LCID\thm.wxl' approach described at https://classicwixburntheme.codeplex.com/. However, I'm having an issue getting the bal:Condition element messages localized accordingly. They always display in English, even though the rest of the UI will display in French for example, when running 'setup.exe -lang 1036' from the cmd line. The strings for these conditions are defined in each of the localized thm.wxl files but they seem to load from the file specified by the WixStandardBootstrapperAllication @ LicenceFile attribute. When using ProcessMonitor I see the following 3 files all being accessed when launching for -lang 1036: ...\.ba1\1033.thm.wxl ...\.ba1\1036.thm.wxl ...\.ba1\thm.wxl Is this method of localizing Burn Condition elements supported? If not, what are my possible workarounds or alternate approaches? Thanks, Ryan -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Localizing-Burn-Condition-messages-tp7600408.html Sent from the wix-users mailing list archive at Nabble.com. -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage
Yes, Orca Summary shows it with Platform x64. -Original Message- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: Friday, November 14, 2014 6:33 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage When you open your 64 bit package with Orca and look at the Summary Information does it indicate that it is a 64 bit package? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WixStdBA-launches-32-bit-msiexec-exe-for-a-64-bit-MsiPackage-tp7597932p7597940.html Sent from the wix-users mailing list archive at Nabble.com. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage
OK, so, is there a way I can achieve what I need to achieve? Run this CA in a 64-bit process? -Original Message- From: Rob Mensching [mailto:r...@firegiant.com] Sent: Friday, November 14, 2014 7:53 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage Custom actions are hosted by Windows Installer in a separate custom action host process based on custom action type. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Ryan Waller [mailto:rwal...@microsoft.com] Sent: Friday, November 14, 2014 7:43 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage Yes, Orca Summary shows it with Platform x64. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage
In my case, my CA dll is built as AnyCPU. So it seems I need to build it separately for x86 and x64. I will try that. Thanks! -Original Message- From: Phil Wilson [mailto:phildgwil...@gmail.com] Sent: Friday, November 14, 2014 10:38 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage and by will be built with the caller's architecture I mean JIT compiled to the caller's architecture because this is happening at run time. --- Phil Wilson On Fri, Nov 14, 2014 at 10:29 AM, Phil Wilson phildgwil...@gmail.com wrote: Just to add something that may be the issue with your setup. The call stack is driven by the architecture of the starting process or Dll, so if you have a 32-bit CA Dll then msiexec will be a 32-bit process to call it. Your Dll then calls other Dlls. and If all these other Dlls are AnyCpu then yes, they will work in the sense that you said they can run on any architecture and so will be built with the callers architecture, so you'll get a 32-bit Dll call stack on a 64-bit system. That all works fine until it doesn't because it needs to do something in the 64-bit world, such as look inside a 64-bit process. --- Phil Wilson On Fri, Nov 14, 2014 at 10:10 AM, Phil Wilson phildgwil...@gmail.com wrote: Yes something is checking the platform setting. Your comment is otherwise too vague. Since you need separate setups for 32-bit and 64-bit systems it's often best to make sure that all the code that runs during the install is of the appropriate bitness. You don't want a 32-bit (64-bit) hosting process or Dll trying to call a 64-bit (32-bit) Dll or some other invalid cross architecture thing. --- Phil Wilson On Fri, Nov 14, 2014 at 9:42 AM, Asbjørn Mikkelsen asbj...@neslekkim.net wrote: So something is checking the platform setting on the dll ?, With VS2012 and VS2013, I'm getting problems if I start to set platform to anything else than anycpu on dll's now, what gives? On Fri, Nov 14, 2014 at 6:38 PM, Phil Wilson phildgwil...@gmail.com wrote: To expand on what Rob said, it all just works. On an x64 system the MSI service will be 64-bit. If you have a 32-bit CA you'll get a 32-bit msiexec process launched to host it. If you have another CA that requires impersonation, you'll see another msiexec process running impersonated. The error you're seeing is nothing to do with the with this architecture. It's just invalid for a 32-bit process to access 64-bit modules. You are enumerating processes or you have a process id that's 64-bit and you're using it from 32-bit code to access the process? As Jacob says, if you're on a 64-bit system and you want to do whatever you're doing, make a 64-bit version of your Dll. --- Phil Wilson On Fri, Nov 14, 2014 at 8:35 AM, John Cooper jocoo...@jackhenry.com wrote: That is the technique I use and it is necessary when access 64-bit-only file system locations and the like. -- John Merryweather Cooper Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 | jocoo...@jackhenry.com -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Friday, November 14, 2014 10:32 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage What is the bitness of your CA DLL? Just a stab in the dark but you might need to have it compiled twice, once as 32 and once as 64, and have the respective MSI package use the right CA DLL. -Original Message- From: Rob Mensching [mailto:r...@firegiant.com] Sent: Friday, November 14, 2014 9:53 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage Custom actions are hosted by Windows Installer in a separate custom action host process based on custom action type. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Ryan Waller [mailto:rwal...@microsoft.com] Sent: Friday, November 14, 2014 7:43 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage Yes, Orca Summary shows it with Platform x64. --- --- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http
Re: [WiX-users] FontId descriptions
Thanks Sean! All I had to do was define the new Font in the RTFTheme.xml. -Original Message- From: Sean Hall [mailto:r.sean.h...@gmail.com] Sent: Thursday, November 6, 2014 6:47 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] FontId descriptions The FontId refers to Font elements ( http://wixtoolset.org/documentation/manual/v3/xsd/thmutil/font.html) created in your theme file. On Thu, Nov 6, 2014 at 8:22 PM, Ryan Waller rwal...@microsoft.com wrote: Where can I find a list of the supported FontIds and their descriptions, for use with Theme elements used in the RTFTheme.xml in WixStdBA? For example, I'd like to change the FontID of the Text element to Bold, and maybe even Orange color. http://wixtoolset.org/documentation/manual/v3/xsd/thmutil/text.html I'm using Wix 3.9 and am having issues using ThmViewer.exe to preview FontId selections because oftentimes my built BA shows something completely different. Ryan -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WixStdBA launches 32-bit msiexec.exe for a 64-bit MsiPackage
I'm using the WixStdBA to conditionally install either a 32-bit or a 64-bit MsiPackage. When my 64-bit package is installed a 32-bit version of msiexec.exe is launched. Is there way to force the 64-bit msiexec.exe to get launched? My MSI has a custom action to check for a running process and verifies the path of the process using Process.MainModule.FileName but this throws the following execption from a 32-bit msiexec.exe when querying the modules of a running 64-bit app. System.ComponentModel.Win32Exception (0x80004005): A 32 bit processes cannot access modules of a 64 bit process. Thanks in advance, Ryan -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] FontId descriptions
Where can I find a list of the supported FontIds and their descriptions, for use with Theme elements used in the RTFTheme.xml in WixStdBA? For example, I'd like to change the FontID of the Text element to Bold, and maybe even Orange color. http://wixtoolset.org/documentation/manual/v3/xsd/thmutil/text.html I'm using Wix 3.9 and am having issues using ThmViewer.exe to preview FontId selections because oftentimes my built BA shows something completely different. Ryan -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bootstrapper runs msiexec elevated which causes my MSI CustomAction to run elevated
I've authored an MSI package that uses a CustomAction to launch an application after install completes. The package requires elevation but the CustomAction is scheduled after InstallFinalize to launch the application as the Standard User, not elevated. When installing the MSI alone using msiexec.exe, things work as expected, and my application launches correctly as the Standard User. However, we're using the WIX Standard BA bootstrapper to chain this package in a install bundle. The problem is, when this MSI package runs as part of the BA, it runs elevated, and so too does the CustomAction, which in turn launches the app elevated, which is not what we want. It seems that the BA launches msiexec.exe elevated. Is there a way to keep the BA from launching the MSI elevated? Thanks in advance, Ryan -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper runs msiexec elevated which causes my MSI CustomAction to run elevated
I've tried that but it requires the user to click a button after install completes, and they can also cancel. Neither is desirable. Can this be invoked without the button click? Ideally I would just like to have my MSI executed without elevation, just like when running msiexec.exe from the command line. -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Monday, November 3, 2014 2:45 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Bootstrapper runs msiexec elevated which causes my MSI CustomAction to run elevated WixStdBA handles this without a CA via: Variable Name=LaunchTarget Value=[ProgramFilesFolder]\Blah\Blah\Application.exe/ -Original Message- From: Ryan Waller [mailto:rwal...@microsoft.com] Sent: Monday, November 03, 2014 4:32 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Bootstrapper runs msiexec elevated which causes my MSI CustomAction to run elevated I've authored an MSI package that uses a CustomAction to launch an application after install completes. The package requires elevation but the CustomAction is scheduled after InstallFinalize to launch the application as the Standard User, not elevated. When installing the MSI alone using msiexec.exe, things work as expected, and my application launches correctly as the Standard User. However, we're using the WIX Standard BA bootstrapper to chain this package in a install bundle. The problem is, when this MSI package runs as part of the BA, it runs elevated, and so too does the CustomAction, which in turn launches the app elevated, which is not what we want. It seems that the BA launches msiexec.exe elevated. Is there a way to keep the BA from launching the MSI elevated? Thanks in advance, Ryan -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
