Hello,
I was trying to replace some text on the deployment UI (attached screen),
it seems could change that text by adding (to a .wxl file in the project):
<String Id="ExitDialogTitle">{\WixUI_Font_Bigger}Replacement text
here</String>
However, our current deployment project does not have .wxl files, instead
it includes some resource dll files from the application, but it seem does
not do anything to the deployment (it has localization for the
application). I am wondering can I use that resource dll file instead of to
create new .wxl file? If it is not possible to do it from the resource dll
file, so it might be mistake we include dlls into the deployment, or maybe
we mixed up the application localization with installer location wrong, ?
Thanks,
Does this dll includes make any sense at all?
<!-- The Engish Localization DLL goes into the program root -->
<Component Id="Localization_en">
<File Id="LocalizationDLL"
Name="Localization.Dll"
Source="$(var.productxxx_Path)\Localization.dll"
/>
</Component>
<!-- Each of the other 8 languages to into their respective
subdirectories -->
<Directory Id="de" Name="de">
<Component Id="Localization_de"
Guid="{48cae4cf-ab9e-4ee4-a54f-24974a37116f}">
<File Id="Resources.de" Name="Localization.resources.dll"
Source="$(var. productxxx _Path)\de\Localization.resources.dll" />
</Component>
</Directory>
The following blog mentioned resource dll are for application, not the
deployment??
http://wix.sourceforge.net/manual-wix2/robmen_20041122.htm
So, here's my standard template for success with localization. First,
break out all of the localizable text in your product into a separate
resource-only
DLL<http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/html/_core_Create_a_Resource.2d.Only_DLL.asp>.
Second, put that resource-only DLL in a sub-directory named for the
language of the resource-only DLL. Keep the name of the resource-only DLL
the same though. Since I'm an old Office guy, I usually use the
LCID<http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/nls_8sj7.asp>(1033
is American English) for the directory name but I've seen the trend
towards using the ISO locale names (en-us is American English) since the
Common Language Runtime goes that way. Third, store the default
installation's language in your per-application data store. For example,
an HKLM registry key is an okay store if your product was installed
per-machine and an HKU registry key would be okay if your product was
installed per-user. The Registry/@Root="HKMU" value in Windows Installer
XML syntax was designed for this type of scenario. Fourth, store the
user's current language preference in a per-user data store (a per-user
registry key works okay) when it differs from the installed value.
Finally, when you boot your application load the resource-only DLL from the
appropriate sub-directory based on the per-user key if it exists and the
per-application key if it does not exist.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
