Use autogenerated GUIDs and don't worry about it.
On Tue, Oct 30, 2012 at 9:52 PM, Nick Ramirez wrote:
> 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 a
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
inst
Yes. Loc variables are not intended to be used the way you are doing them.
On Tue, Oct 30, 2012 at 9:23 PM, Nick Ramirez wrote:
> This is not a big issue, really just something I stumbled on and am curious
> about. If I use a localization variable in a component's GUID, like this:
>
> /
>
>
This is not a big issue, really just something I stumbled on and am curious
about. If I use a localization variable in a component's GUID, like this:
/
/
And then add a .wxl file:
/
http://schemas.microsoft.com/wix/2006/localization";>
*{872EAAB7-BDE1-4EF4-89C6-97664705CB0F}*
/
I've notic
4 matches
Mail list logo
