Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??
This worked well. Thank you.James From: Phill Hogland [via Windows Installer XML (WiX) toolset] ml-node+s687559n7598508...@n2.nabble.com To: James unk...@yahoo.com Sent: Tuesday, 9 December 2014, 14:30 Subject: Re: Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue?? Define a variable in your bundle, detect the culture in your BA, and set this variable (or use one of the Burn built-in language variables). You could take different approaches here, but the result is that you use the variable in your InstallCondition to determine which of the msi packages will be installed (or use the information in the OnPlanPackageBegin handler to select whether a particular package will be installed or not.) In the example you would replace 'App' with 'Final_SF1', I assume. When you add the following to your chain, all of the PackageGroupRef related to specific cultures, in the example, are included in your chain in the sequence that you authored them. Chain ...Prerequisites ...other stuff PackageGroupRef Id='Final_SF1' Then you need to author the other parameters of the MsiPackage elements so that burn can find the msi packages and you have InstallConditions that specify whether the package is installed. I use the following but you might have different requirements. Variable Name='MyNumericVar' Value='1033' Type='numeric' bal:Overridable='yes'/ I set the var in my ba to an lcid. InstallCondition='MyNumericVar=1031' (true when installing de-DE, otherwise not installed) If you reply to this email, your message will be added to the discussion below: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7598508.html To unsubscribe from Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??, click here. NAML -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7598625.html Sent from the wix-users mailing list archive at Nabble.com. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??
Hi, Thank you for your quick response. I didn't get this quite clearly. Can you please help? Attached is my bundle.wxs file. There are few thing I am not very sure how to do. Some background before the queries. The bundle.wxs pacages 3 MSI's. Prerequisite(1), ResourceFolder(2) and Final_SF1(3). They are to be called in sequence I mentioned. The only MSI which has GUI and is localized is Final_SF1. This localized MSI's are available in the respective folders (SourceFile=..\Final_SF1\bin\$(var.Platform)\$(var.Configuration)\cs-CZ\Final_SF1.msi) from my build script in respective language folders. I have created fragments as mentioned in earlier reply for few languages. Now the issues. 1. How does I fit these localized MSI's into the sequence of execution? 2. How the bundle knows (or rather I tell bundle) which langaueg Final_SF1 MSI is to be called/executed? 3. And the current code fails to build saying error CNDL0005: The Chain element contains an unexpected child element 'PackageGroup' Am I missing something obvious ? What changes I need to do in my bundle.wxs. Regards, James From: Phill Hogland [via Windows Installer XML (WiX) toolset] ml-node+s687559n759845...@n2.nabble.com To: James unk...@yahoo.com Sent: Friday, 5 December 2014, 11:21 Subject: Re: Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue?? Based on input in this thread I concluded that using embedded transforms would not work in a Burn driven scenario reliably. At the time I had difficulty understanding how to allow the packages to be created with multiple cultures in separate output folders and then pull those back into the bundle. I posted this question and got good advice. http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-external-cab-for-multiple-language-msi-packages-td7596991.html When a package builds, it uses an external cab file, and builds the output of that package project to separate culture named output folders (default behavior of wix). Then in the bundle's I rename the package like this Fragment PackageGroup Id='App' PackageGroupRef Id='App_de_DE'/ PackageGroupRef Id='App_en_US'/ /PackageGroup /Fragment Fragment PackageGroup Id='App_de_DE' MsiPackage Id='App_de_DE' ...stuff... SourceFile='de-DE\App.msi' Name='App\App_de-DE.msi' /MsiPackage /PackageGroup /Fragment Fragment PackageGroup Id='App_en_US' MsiPackage Id='App_en_US' ...stuff... SourceFile='_en_US\App.msi' Name='App\App_en_US.msi' /MsiPackage /PackageGroup /Fragment The packages are not compressed so the renamed msi and related external cab file end up in a sub folder relative to the bundle named App. The tree is much larger than when transforms are used, but since we stage to a server and the customer only gets the small bootstrapper exe (and the packages that their configuration needs), this seems to work for use. Others in this list mentioned using the transforms external to the msi, but I can't speak to that process. If you reply to this email, your message will be added to the discussion below: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7598452.html To unsubscribe from Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??, click here. NAML Bundle.wxs (10K) http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/attachment/7598503/0/Bundle.wxs -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7598503.html Sent from the wix-users mailing list archive at Nabble.com. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??
Define a variable in your bundle, detect the culture in your BA, and set this variable (or use one of the Burn built-in language variables). You could take different approaches here, but the result is that you use the variable in your InstallCondition to determine which of the msi packages will be installed (or use the information in the OnPlanPackageBegin handler to select whether a particular package will be installed or not.) In the example you would replace 'App' with 'Final_SF1', I assume. When you add the following to your chain, all of the PackageGroupRef related to specific cultures, in the example, are included in your chain in the sequence that you authored them. Chain ...Prerequisites ...other stuff PackageGroupRef Id='Final_SF1' Then you need to author the other parameters of the MsiPackage elements so that burn can find the msi packages and you have InstallConditions that specify whether the package is installed. I use the following but you might have different requirements. Variable Name='MyNumericVar' Value='1033' Type='numeric' bal:Overridable='yes'/ I set the var in my ba to an lcid. InstallCondition='MyNumericVar=1031' (true when installing de-DE, otherwise not installed) -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7598508.html Sent from the wix-users mailing list archive at Nabble.com. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??
Hi, Have you found a solution for this? Are there any pointers for this ? I have exactly same issue. -James -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7598436.html Sent from the wix-users mailing list archive at Nabble.com. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??
On Fri, 5/12/14, James [via Windows Installer XML (WiX) toolset] ml-node+s687559n7598436...@n2.nabble.com wrote: Subject: Re: Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue?? To: James unk...@yahoo.com Date: Friday, 5 December, 2014, 9:10 AM Hi, Have you found a solution for this? Are there any pointers for this ? I have exactly same issue. -James If you reply to this email, your message will be added to the discussion below: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7598436.html To unsubscribe from Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??, click here. NAML -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7598437.html Sent from the wix-users mailing list archive at Nabble.com. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??
Based on input in this thread I concluded that using embedded transforms would not work in a Burn driven scenario reliably. At the time I had difficulty understanding how to allow the packages to be created with multiple cultures in separate output folders and then pull those back into the bundle. I posted this question and got good advice. http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-external-cab-for-multiple-language-msi-packages-td7596991.html When a package builds, it uses an external cab file, and builds the output of that package project to separate culture named output folders (default behavior of wix). Then in the bundle's I rename the package like this Fragment PackageGroup Id='App' PackageGroupRef Id='App_de_DE'/ PackageGroupRef Id='App_en_US'/ /PackageGroup /Fragment Fragment PackageGroup Id='App_de_DE' MsiPackage Id='App_de_DE' ...stuff... SourceFile='de-DE\App.msi' Name='App\App_de-DE.msi' /MsiPackage /PackageGroup /Fragment Fragment PackageGroup Id='App_en_US' MsiPackage Id='App_en_US' ...stuff... SourceFile='_en_US\App.msi' Name='App\App_en_US.msi' /MsiPackage /PackageGroup /Fragment The packages are not compressed so the renamed msi and related external cab file end up in a sub folder relative to the bundle named App. The tree is much larger than when transforms are used, but since we stage to a server and the customer only gets the small bootstrapper exe (and the packages that their configuration needs), this seems to work for use. Others in this list mentioned using the transforms external to the msi, but I can't speak to that process. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7598452.html Sent from the wix-users mailing list archive at Nabble.com. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??
Yes exactly we use the language transforms only on localization strings (ActionText, Control, Dialog, Error, RadioButton + UIText...). In Property Table we change: ProductLanguage and add an additional Dummy Property for an English Transform. We don't change: ProductCode + Languages (In SummaryInformation) and PackageCode + UpgradeCode What you have may work in very narrow cases (i.e. transforms don't change ProductCode, UpgradeCode, Language, etc). For now I expected that approach having no drawback when using in a burn bundle. What might be areas which might have issues or need special consideration? 2014-09-19 19:05 GMT+02:00 Rob Mensching r...@firegiant.com: What you have may work in very narrow cases (i.e. transforms don't change ProductCode, UpgradeCode, Language, etc). _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Tobias S [mailto:tobias.s1...@gmail.com] Sent: Friday, September 19, 2014 6:36 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue?? Not a great solution for localizing shortcut names or service descriptions today. Typically recommend sticking to using trademarked names that aren't localized. Language transforms just aren't supported by Burn yet. Rob you are considering embedded transforms approach in that statement, or? The normal way using MsiPackage Id=MyPackage SourceFile=ADMO_2.30_x86.msi MsiProperty Name=INSTALLDIR Value=[InstallFolder]/ MsiProperty Name=TRANSFORMS Value=[CurrentBurnLanguageName]_x86.mst/ PayloadGroupRef Id=LangMst/ /MsiPackage should be a proper working approach, or did I miss something? -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??
Thank you for the assistance. Phill -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7596918.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??
Not a great solution for localizing shortcut names or service descriptions today. Typically recommend sticking to using trademarked names that aren't localized. Language transforms just aren't supported by Burn yet. Rob you are considering embedded transforms approach in that statement, or? The normal way using MsiPackage Id=MyPackage SourceFile=ADMO_2.30_x86.msi MsiProperty Name=INSTALLDIR Value=[InstallFolder]/ MsiProperty Name=TRANSFORMS Value=[CurrentBurnLanguageName]_x86.mst/ PayloadGroupRef Id=LangMst/ /MsiPackage should be a proper working approach, or did I miss something? -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??
Tobias, that is the approach which I use, embedding the language transforms and setting MsiProperty TRANSFORMS=:langid.mst. I thought that I had tested this successfully several months back when using Wix 3.8, but now I am see two problems documented above. Once installed, say with the German :1031.mst transform later when the bundle is launched to do an uninstall, the plan shows that the package is absent. Also seeing problems with on-demand installs, which I am certain was working in the same scenario with Wix 3.8. so I am curious if others are seeing these issues, or if I should just not try to use language transforms with Burn. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7596923.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??
Sorry misunderstanding. I was not sure whether Rob was talking about the embed MST in MSI approach or the embed MST in Bundle.exe approach. Personally I don't like the embed MST in MSI approach (comp. e.g. http://www.installsite.org/pages/en/msi/articles/embeddedlang/) and use the embed MST in Bundle approach. And here I wasn't sure after Rob's statement whether this causes trouble or not. -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??
What you have may work in very narrow cases (i.e. transforms don't change ProductCode, UpgradeCode, Language, etc). _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Tobias S [mailto:tobias.s1...@gmail.com] Sent: Friday, September 19, 2014 6:36 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue?? Not a great solution for localizing shortcut names or service descriptions today. Typically recommend sticking to using trademarked names that aren't localized. Language transforms just aren't supported by Burn yet. Rob you are considering embedded transforms approach in that statement, or? The normal way using MsiPackage Id=MyPackage SourceFile=ADMO_2.30_x86.msi MsiProperty Name=INSTALLDIR Value=[InstallFolder]/ MsiProperty Name=TRANSFORMS Value=[CurrentBurnLanguageName]_x86.mst/ PayloadGroupRef Id=LangMst/ /MsiPackage should be a proper working approach, or did I miss something? -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??
No. It's the fact that transforms change the package's identity. Essentially, Burn needs to be taught how to figure out all the possible permutations the transforms can provide. You could *maybe* do it manually by exploding out the matrix of Packages x Transforms. Not sure. It's not easy. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Tobias S [mailto:tobias.s1...@gmail.com] Sent: Friday, September 19, 2014 7:26 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue?? Sorry misunderstanding. I was not sure whether Rob was talking about the embed MST in MSI approach or the embed MST in Bundle.exe approach. Personally I don't like the embed MST in MSI approach (comp. e.g. http://www.installsite.org/pages/en/msi/articles/embeddedlang/) and use the embed MST in Bundle approach. And here I wasn't sure after Rob's statement whether this causes trouble or not. -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??
1. AFAIK, nothing changed in WiX v3.9 in that area. 2. This is essentially the same feature request for Burn to support instance transforms. Very challenging. I think Bob would say use language packs. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: Thursday, September 18, 2014 9:08 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue?? I would appreciate advice on deploying applications that support multiple cultures. I am using a Bundle with many none-UI MSI packages for various applications in my product 'suite' (bundle.exe). I currently build the MSI packages and use the process described below to embed language transforms into a 'base' msi package. I then include only the 'base' package in my bundle and pass the TRANSFORM property set to the embedded transform when installed on a non-default (en-US), but company supported culture. http://wix.tramontana.co.hu/tutorial/transforms/morphing-installers While this approach has been working for some time, I am having second thoughts about using the EmbedTransform.exe approach. I have noticed two problems, and while I am not totally sure of the cause of either problem,they do not seem to happen in a (very simple experiment) when I do not use the language transform but deploy separate culture specific MSI packages. Problem 1 is that when I use and advertised feature, and I used the embedded transform, while everything installs successfully when the embedded language transform is NOT used, when it is used the 'on-demand' portion of the setup (after the initial install of the advertised feature and the user clicks on the shortcut for the first time) fails indicating that the package cannot be located. (See comment below about Wix 3.8, as I am sure that this previously worked.) Problem 2, is (after resolving the above issue by not advertising the feature and doing a full local install of the MSI package) then after a successful 'install' of the bundle.exe (suite), later when I do an 'uninstall' of the bundle, it succeeds, but each MSI package for which an embedded transform was used, in the Planning stage is listed as 'absent', hence there is no effort to uninstall it, and it gets abandoned on the system. In my simple experiment when I did not use the embedded transform the package is uninstalled. I am using Wix 3.9.901. The last time I did this type of culture testing I was back on Wix 3.8 and I don't think that these problems existed. So I suspect that there may be a problem with Burn package detection in Wix 3.9. Any thoughts? I am also wondering in general if there is advice as to the wisdom of using EmbedTransform.exe, as I am now having second thoughts. Any thoughts? Thanks for the advice. Phill -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??
I think Bob would say use language packs. I am a little confused by this comment. The translated strings in the current .mst are for things like localizing various MSI error messages (down-version and CA) and to localize descriptions related to installed shortcuts and services (on Windows resources created by the MSI package). The application's localization files are handled independently (which is what I think of as a language pack.) OK on v3.9, I did not do enough testing to be certain of a relationship. I also did not realize the relationship to an InstanceTransform. So does that imply that the process documented in the tutorial is not recommended when using Burn? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7596899.html Sent from the wix-users mailing list archive at Nabble.com. -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??
Not a great solution for localizing shortcut names or service descriptions today. Typically recommend sticking to using trademarked names that aren't localized. Language transforms just aren't supported by Burn yet. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: Thursday, September 18, 2014 11:53 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue?? I think Bob would say use language packs. I am a little confused by this comment. The translated strings in the current .mst are for things like localizing various MSI error messages (down-version and CA) and to localize descriptions related to installed shortcuts and services (on Windows resources created by the MSI package). The application's localization files are handled independently (which is what I think of as a language pack.) OK on v3.9, I did not do enough testing to be certain of a relationship. I also did not realize the relationship to an InstanceTransform. So does that imply that the process documented in the tutorial is not recommended when using Burn? -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
