Re: [WiX-users] burn bootstrapper access -lang as a property or variab le

I currently use an mba which has my bundle strings in the C# mba project. I use the wxl files for my localized msi packages, for localized shortcut descriptions, etc. My bundles rely on default behavior of Burn to use the -lang switch if it exists otherwise select the correct local based on the s

Re: [WiX-users] burn bootstrapper access -lang as a property or variab le

I have been attempting to use the localization files to do this type of thing, but no matter what I try, the variables don't use the localized values. (Again, the UI shows the localized values, but the variables i.e. LanguageID or !(loc.LanguageID) always use the not localized values). Is this a

Re: [WiX-users] burn bootstrapper access -lang as a property or variab le

Jacob makes good points, but I used the information that in the previous links. When using the WixStdBA, since as you found "the bootstrapper is correctly switching to the localized 1046\thm.wxl and 1046\license.rtf" you can take advantage of that fact by: 1) define a Variable element which is ove

Re: [WiX-users] burn bootstrapper access -lang as a property or variab le

PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] burn bootstrapper access -lang as a property or variab le I'm afraid the provided link hasn't helped me solve my problem. I am trying to get the bootstrapper and the MSI to both be translated into the same language. When

Re: [WiX-users] burn bootstrapper access -lang as a property or variab le

I'm afraid the provided link hasn't helped me solve my problem. I am trying to get the bootstrapper and the MSI to both be translated into the same language. When the user enters the -lang 1046 as a command line parameter for the bootstrapper, the bootstrapper is correctly switching to the local