Merge of Loc PRI file failed calling makepri.exe: '0x80073B08'

Question

1>  Multilingual App Toolkit build started.
1>  Merge of Loc PRI file failed calling makepri.exe: '0x80073B08'
1>  Multilingual App Toolkit build completed with errors.

I can't seem to be able to find any Information on this and tried to add localization support exactly as described here:

http://channel9.msdn.com/posts/Build-Multi-language-apps-using-the-Multilingual-App-Toolkit

Any ideas?

Answer 1

This error code indicates that a (localized) resource add was attempted, but the source resource is not in the PRI file. Three conditions were recently discovered that can cause this condition for resources.

• A duplicate resource exists in the resjson file.
  JavaScript Example:
  "Cancel" : "Cancel"
  "cancel" : "Cancel" <-- Duplicate resource

• A resource ID conflicts with a different resource with the same base path information.
  JavaScript Example:
  "About" : "About title"
  "About/OKBtn" : "OK". <-- Resource path is the same as a previous resource's ID

  XAML Example:
  MyButton : "Button without property"
  MyButton.Content : "Hallo Welt" <-- Becomes "MyButton/Content", which conflicts with the "MyButton" ID

• A resource ID contains the same name as the resource file.
  Common Example:
  Filename: Resources.resjson
  "Dialog/Resources/Title" : "Welcome"

Please look for these conflicts as they are know to cause this error message. You could also see this error on the preview version. Please ensure that you are running the released version of the toolkit - it is v1.0.1114.0.

Answer 2

A new version of the Multilingual App Toolkit has been released that will help identify when this issue happens so you can easily adjust the resources.  All three known issues are resolved with this release.  The version is v1.1.1075.0 as displayed in the VS IDE Extensions and Updates dialog.

Answer 3

so how would one for example localize a TextBlock with a Text and a Tooltip?

since you can't use "MyTextBlock.Text" and "MyTextBlock.Tooltip" at the same time...

it basically breaks the x:Uid based approach of localizing, doesn't it?

So I would have to call {x:Static ...} or some Markupextension like {l:Translate ...} and give everything a unique key, or is there a better way?

Answer 4

hm or is the real problem the extended property format?

e.g.: ClearNotesButton.[using:Windows.UI.Xaml.Controls]ToolTipService.ToolTip