Re: [WiX-users] Verb localization

Might be a bug in MSDN documentation. Then you're left with creating language transforms for each language, embedding them in the MSI, and setting the TRANSFORMS property with the language Id from WiX's bundle. - Nir Bar Freelance Developer Mail: nir@panel-sw.com Web: www.panel-sw.com

Re: [WiX-users] Verb localization

I have checked it. In Verb table for verb "NewVerb" command is "[NEW_VERB_COMMAND]". In properties table Property "NEW_VERB_COMMAND" with value "MyValue" exists. Is it bug in MSI or WIX or something else? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nab

Re: [WiX-users] Verb localization

That's strange... Verb table's Command field is documented to have Formatted type which expands properties. Can you check the Command field of Verb table in

Re: [WiX-users] Verb localization

It has no effect:( Now I see "[NEW_VERB_COMMAND]" in context menu. Any Ideas? Here is small example of using it. http://schemas.microsoft.com/wix/2006/wi";>

Re: [WiX-users] Verb localization

You should use . - Nir Bar Freelance Developer Mail: nir@panel-sw.com Web: www.panel-sw.com - C++ On Windows, Linux and Embedded Platforms - WiX & InstallShield -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Verb-localization

Re: [WiX-users] Verb localization

Nir, thanks for ypu answer. But how I can lounch MSI with correct mst file from bootstraper? About Property. I can't use property for it. I tried it. But when I use Property name in command attribute. It is not replaced by its value. ... Command is "NEW_VERB_COMMAND"

Re: [WiX-users] Verb localization

Windosw Installer localization is achieved using transforms (mst files) that can be embedded in a single multi-lingual MSI. You should use WiX localization