![\".NET](\"https:\/\/devblogs.microsoft.com\/heaths\/wp-content\/uploads\/sites\/13\/2006\/06\/ndp_patch_ui.png\")
<\/p>\nWhen you download a patch for .NET Framework 2.0 and double-click to install\nit, you'll find that the dialog is missing some text as in the example below.<\/p>\n
<\/p>\n
This is due, in part, to a bug in Windows Installer when the\n\nProductLanguage property<\/a> is 0 in the\n\nProperty table<\/a>.<\/p>\n Windows Installer contains localized string tables for some basic text like\nfor the Cancel button, and some errors that may be returned if the package can't\nbe opened, a patch cannot be uninstalled, and other issues mainly before a\npackage can even be loaded. Until the package is loaded and the ProductLanguage\nproperty is read, Windows Installer uses the user's default user interface\nlanguage; after that, language resources are used according to the\nProductLanguage property value. Localized strings are expected to be found in\nthe\n\nActionText table<\/a> and the\n\nError table<\/a>, which includes strings such as Error 20, typically read in\nEnglish as "Please wait while Windows configures [ProductName]", which should be\ndisplayed in the dialog above.<\/p>\n In Windows Installer 3.1 and prior, when ProductLanguage is 0 Windows\nInstaller does not pick the right strings in another resource – a binary\nresource – nor does it even contain a lot of strings commonly found in the Error\ntable. This is now fixed in Windows Installer 4.0 for Windows Vista.<\/p>\n Since the right common Error strings were not properly selected, the setup\nbuild team did not merge resources into the ActionText and Error tables. It was\ndecided that displaying no text is better than displaying only English text.\nBefore being released, this was also the case for Visual Studio 2005 but since\nVS was language-specific we made sure they merged the correct ActionText and\nError table strings into the .msi<\/i> file. To display localized strings in\npopup dialogs for language-neutral products where ProductLanguage = 0, we do\nembed "resource merge modules". These are .msm<\/i> files that contain\nlocalized resources such as error strings and dialogs. When necessary, we\nextract a .msm<\/i> file according to the user's default user interface\nlanguage and extract what strings or dialogs we need. We cannot, unfortunately,\nuse that approach to provide strings used in the\n\nbasic UI<\/a> you see above.<\/p>\n The wrapper that ships with the .NET Framework 2.0 redistributable is an\nexternal UI handler that does not, unfortunately, use localized transforms but\ninstead processes messages from Windows Installer and displays localized text\nbased on those messages. Since transforms are not used, no transforms are cached\nalong with the product package so the patch UI will not contain text for some\ncontrols.<\/p>\n To fix this you can create a transform that will add localized strings to the\nActionText and Error tables. You can do this in Orca, for example, following the\ninstructions below.<\/p>\n \t\n
dotnetfx.exe \/c \/t:"%CD%dotnetfx"<\/code>
\n <\/li>\n