ok thanks Rob. That explains why I haven’t found an easy way to do this.
I’m trying to replace our old InstallAware installer with WiX. Generally I’m much happier with what I have localized with WiX than with InstallAware. However, with InstallAware we did localize the Program & Features name for previous releases, so if possible I’d like to localize it with WiX, so our non-English users aren’t confronted with in incomprehensible (English) name in Programs & Features. Do I understand correctly that to localize the name in Programs & Features, I need to create a BAfunctions.dll in which I set WixBundleName based on the current language of the user’s computer? If so, I’m back to this question: When building the BAFunctions sample program at src\burn\Samples\bafunctions, I get: Error 1 error C1083: Cannot open include file: 'IBootstrapperBAFunction.h': No such file or directory c:\downloads\wix39-debug\src\burn\samples\bafunctions\precomp.h 51 1 bafunctions With VS2010 I get the same error whether I use the latest WiX v3.10 or 3.9 R2. Is the sample supposed to build? I’m not sure where to start. Any guidance would be appreciated! Thanks, David > On Mar 30, 2015, at 4:26 PM, Rob Mensching <r...@firegiant.com> wrote: > > Often the Programs & Features contains the name of the product which is > typically a trademark (or treated like a brand in any case) and thus not > localized. > > It's possible to change the name but wixstdba doesn't really expose it easily. > _____________________________________________________________ > Short replies here. Complete answers over there: http://www.firegiant.com/ > > > -----Original Message----- > From: David Burson [mailto:david_bur...@ntm.org] > Sent: Monday, March 30, 2015 9:53 AM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] BAFunctions.dll to set WixBundleName from the > language of the user's computer > > Thanks Phil, > > I’m just trying to make sure that when a user tries to uninstall my software, > they can find it in Programs & Features (or when they are looking through > Programs & Features, they don’t uninstall it because they don’t know what it > is). That means the name that Programs & Features displays needs to be what > they think of as the name of my program, which is different for each > language. I’d obviously rather not write my own BAfunctions.dll if I can > avoid it. I’m new to all this so I appreciate your patience as I try to > understand my options. > > I’ve studied the link you provided and the other links in it, but still have > not come up with a working solution. Towards the beginning of the discussion > you referenced below, you provided a link on how to localize the Product name > of an msi, and said "(It happens to be in a MSI Product element but also > could be implemented in a Bundle element.)” But when I add a string for > “WixBundleName” to my wxl’s, it seems to be ignored. > Here<http://stackoverflow.com/questions/29266905/wix-toolset-how-to-create-a-single-exe-with-product-name-localized-for-multiple/29270124?noredirect=1#comment46810219_29270124> > is my SO question, which led me to think I need to create a BAfunctions.dll. > I thought it might be more appropriate to move my ongoing questions to this > email list, rather than continue in SO - please correct me if I’m wrong! > > Anyway, thanks to a number of posts by you and others (and the wix toolset > site), my installer works great. All strings (including the name of my > program) are presented in the user’s language. The one issue left is the > name that is displayed in Programs & Features. In my SO question above the > original answer mentioned a cool feature not yet being worked on that, if I > understand correctly, will localize the name in Programs & Features even if > the user changes languages after installing the program. While that may be > ideal, it’s more than I need. > > Really, all I need is for Programs & Features to display the same name I show > to the users at install time. Currently that is a variable I define for each > language I support, since I’ve not been able to figure out how to change > [WixBundleName]. > > Some of my constraints: > > - I cannot go the route of including different msi’s in my bundle (one per > language), since each msi is about 250 MB. > - I cannot simply have my users download the appropriate msi for their > language. Typical distribution (which I can’t control) is an English speaker > installs the software for themselves, and gives their installer to nationals > who don’t speak English. So the single installer needs to “just work” for > the languages I support. > - Additionally, many of my users have no reliable internet connection. > > My program does not use .NET. I’m not currently using Visual Studio, though > if necessary in order to solve this issue I have VS 2010 and of course the > free VS 2013 available. I just can’t add .NET or other large dependencies. > > Another path I’ve gone down is to not give my bundle a name at all, and set > Visible=“yes” in my msipackage, and try to figure out what Tobias S meant by > the “normal” way in this > conversation<http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-td7596896.html>. > That works fine, even though uninstalling from Programs & Features doesn’t > use my bundle UI (I can live with that), but the deal-killer is that after > uninstalling via Programs & Features, when I try to re-install by running my > installer, it thinks it’s still installed. Which makes sense - the bundle is > distinct from the program I’m installing - but the user doesn’t see it that > way. > > I’m still trying to understand: am I really the only person that needs a > single installer without duplicating an msi for each language, and needing to > localize the program name in Programs & Features? How do people normally do > this? Surely it’s not normal to rely on users knowing enough English to > understand the English name of every program they install, and be able to > figure out from the English name what program it is? > > Thanks very much for any guidance anyone can give me! > > David > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
