Oh, glad I asked then. The way that I've done localizable text in software has been to use a satellite assembly. In that case, I think that each set of localized strings gets its own assembly (if I am remembering that correctly). Maybe best practice is to include all of these assemblies in the install, but possibly only install the "extra" language assemblies if some optional Feature is selected. (In that case, localization variables probably aren't necessary and everything is handled by including components in the proper features.)
I just thought that there might be a situation where someone would want to change the GUID on a component if the MSI is built for a different language? If that ever happens (and it may not), is using a localization variable not the best way to go about switching the GUID on a component? I'm a little out of my depth here. Is this something that isn't really ever done? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Localizing-component-GUIDs-tp7581681p7581684.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
