Multilingual App Toolkit


The Multilingual App Toolkit works with Visual Studio to streamline your localization workflow for Windows Store, Windows Phone and desktop apps. The toolkit helps you localize your apps with localization file management, translation support, and editing tools.

(4) Review
Visual Studio
2013, 2012
Get now (21,582)
E-mail Twitter Digg Facebook
Add to favorites
Reviews (4)
Q and A (5)
Sign in to write a review
Sort by:

by MatiasW8 | August 14 2014

by Joker-Obama | June 27 2014

Can't uninstall!!!!!!!!!!!!!!!!!!!!!!!

World-Readiness Team June 27 2014
| Edit |

Please uninstall v3.0 first. We fixed a bug in setup, but the fix does requires you to install v3.0 manually first. Going forward, you will be able to upgrade.

by Ben Riga - Microsoft | April 10 2014

by Arian Kulp | December 06 2013

Makes it so easy to localize your app! Highly recommended!

Sign in to start a discussion

  • Broken VS 2012
    14 Posts | Last post July 26, 2014
    • Anyone else having issues with existing apps?  Getting the following when VS loads the project and this when I try to compile or debug:	
      1	The file exists.
      2	Update XLIFF build failed.	
      3	Multilingual App Toolkit build completed with errors.
          <description>System.IO.IOException: The file exists.&#x000D;&#x000A;&#x000D;&#x000A;   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)&#x000D;&#x000A;   at System.IO.__Error.WinIOError()&#x000D;&#x000A;   at System.IO.Path.InternalGetTempFileName(Boolean checkHost)&#x000D;&#x000A;   at System.Windows.Input.Cursor.LoadFromStream(Stream cursorStream)&#x000D;&#x000A;   at System.Windows.Input.Cursor..ctor(Stream cursorStream)&#x000D;&#x000A;   at Microsoft.VisualStudio.Text.Editor.Implementation.LeftSelectionMargin.get_RightArrowCursor()&#x000D;&#x000A;   at Microsoft.VisualStudio.Text.Editor.Implementation.LeftSelectionMarginProvider.CreateMargin(IWpfTextViewHost textViewHost, IWpfTextViewMargin containerMargin)&#x000D;&#x000A;   at Microsoft.VisualStudio.Text.Utilities.ContainerMargin.&lt;AddMargins&gt;b__2(IWpfTextViewMarginProvider mp)&#x000D;&#x000A;   at Microsoft.VisualStudio.Text.Utilities.GuardedOperations.InstantiateExtension[TExtension,TMetadata,TExtensionInstance](Object errorSource, Lazy`2 provider, Func`2 getter)</description>
    • Same error here. I've raised a question on SO but no response.
      I've tried installing older version, but same error persists.
    • try this link:
    • Well that solution work for a while, now back to the same error.  I'm seeing other on the net having the same problem.
    • SamVM, I'm looking into this issue but am having a hard time creating a repro. Can you enabled the toolkit and perform a build in Detailed mode? (Tools->Options->Projects and Solutions->Build and Run and set "MSBuild project build out verbosity" to Detailed?  Also, any environment details as well.
      I only need the section between the start and end reports
      1>  Multilingual App Toolkit build started.
      1>  Multilingual App Toolkit build completed successfully.
      This feels like a file is trying to be created, but already exists, but I'm not able to narrow it down  - yet.
    • Hi Cameron,
      I've replied to the query in the MSDN forum (
      It is working fine for me now, but I'll keep you posted here in case of any errors.
    • I'm still having the problem, I'll run it, where is the output for this located.
    • This might help, MultilingualPhoneBuild is an invalid child element in the XML listed below:
        <!-- Define the build task and parameters -->
        <Target Name="MultilingualAppToolkit" AfterTargets="BeforeBuild">
    • Here is the complete error:
      The element 'Target' in namespace '' has invalid child element 
      'MultilingualPhoneBuild' in namespace ''.
       List of possible elements expected: 'Task, AL, AspNetCompiler, AssignCulture, AssignProjectConfiguration, AssignTargetPath, 
      AxImp, CallTarget, CombinePath, ConvertToAbsolutePath, Copy, CreateCSharpManifestResourceName, CreateItem, CreateProperty, 
      CreateVisualBasicManifestResourceName, Csc, Delete, Error, Exec, FindAppConfigFile, FindInList, FindUnderPath, FormatUrl,
       FormatVersion, GenerateApplicationManifest, GenerateBootstrapper, GenerateDeploymentManifest, GenerateResource,
       GenerateTrustInfo, GetAssemblyIdentity, GetFrameworkPath, GetFrameworkSdkPath, GetReferenceAssemblyPaths, LC,
       MakeDir, Message, Move, MSBuild, ReadLinesFromFile, RegisterAssembly, RemoveDir, RemoveDuplicates, 
      RequiresFramework35SP1Assembly, ResolveAssemblyReference, ResolveComReference, ResolveKeySource, ResolveManifestFiles, 
      ResolveNativeReference, ResolveNonMSBuildProjectOutput, SGen, SignFile, TlbImp, Touch, UnregisterAssembly, 
      UpdateManifest, Vbc, VCBuild, Warning, WriteCodeFragment, WriteLinesToFile, XslTransformation, CodeAnalysis, CL, 
      Link, BSCMake, CPPClean, Get....	
      C:\Program Files (x86)\MSBuild\Microsoft\Multilingual App Toolkit\Microsoft.Multilingual.WindowsPhone.targets	9	6	Miscellaneous Files
    • HI JohnWarns - The above error is different from the original problem that was reported.  Can you mail me Cameron dot lerum at outlook dot com so I can help get you going again?
    • email is in you inbox
    • The problem turned out to be related to hitting the limit of temp files that can be created by the System.IO.Path.GetTempFileName() API (see:;k(GetTempFileName);k(TargetFrameworkMoniker-.NETFramework,Version%3Dv4.5);k(DevLang-csharp)&rd=true)
      Once the temp files from all the different process (beyond MAT) were cleaned up, the problem no longer occurs.  If you hit this issue, please be sure to clean your %temp% folder to get unblocked.
    • I'm having the same issue now, i've cleaned my TEMP folder and it doesn't help.
    • MagicMax,
      Sorry to hear you are seeing this issue. Newer versions of MAT should not be subject to this problem.  I would like to get some more information is possible.  Can you send me the log file from your builds as well as the version of VS and MAT that you are running?  If so, please send it to and I'll take a look.  if you have a sample project that repro the problem, that might help as well.
  • Windows 7 support (WPF applications)
    3 Posts | Last post June 13, 2014
    • Is it possible to install the Visual Studio add-in on Windows 7? 
      I'm interested in using the MAT to localize a WPF application, but I don't seem to have any menu available to enable it. I think that the extension isn't actually installed, although the localisation editor is (no apparent errors, just no installation). I'm using VS2013 Premium on Windows 7 Enterprise x64.
    • James,
      This was a miss in our setup changes. It does work on a Windows 7 environment for desktop apps, but setup is blocking the VS components.  We will fix this with the next release.  
    • Any idea on how far away the next release with this feature is?
  • PCL Project support
    2 Posts | Last post February 08, 2014
    • How can I use Multilingual App Toolkit on a PCL Project and share the translation with my others projects (Xamarin.iOS and Xamarin.Android)?
    • PCLs are not currently supported, but this is something worth considering. I would recommend creating a request on the User Voice site for MAT ( for the PCL support so that others can add their voice to the request as well.
      The Xamarin.iOS and Xamarin.Android take a different, platform specific resourcing model that MAT does not support. Besides another user voice request, I would recommend looking at MVP Chris Miller's blog using MAT in with Xamarin and cross-platform development. Here is his blog:
  • Changelog
    3 Posts | Last post October 02, 2013
    • This is a great toolkit, but does anyone have the most recent changelogs? If possible, the changelog from 1.2 -> 2.0 and then from 2.0 -> 2.1.1.
    • Thanks for the great toolkit remark :-)
      Here is a quick list:
      1.2 to 2.0
      - Added support for Visual Studio 2013 Preview
      - Translation Suggestion support – exposed via the editor
      - Multiple same language provider support (If the first provider does not find a translation, or high enough confidence level, the next provider in the list is checked)
      - Support for 3rd party translation providers.
      - Addition of a “Recycle XLIFF Translation” which allows you to quickly select XLF files from other projects to recycle based on exact match.
      - Multi-selection of XLF files in the IDE for Generate, Send, Import and Recycle
      - Send for Translation and Import Translation compressed file support.
      - Bug fixes
      2.0 to 2.1
      - Added the Microsoft Language Portal translation provider (See:
      - Custom metadata support for 3rd party translation providers.
      - Improved stability and usability in the Editor via improved hotkey and discoverability via tooltip support.
      - Improved error and message reporting for both local and TFS builds
      - Improved XLIFF data round tripping support
      - Pre-population of XLIFF resources in new languages after the toolkit is enabled and built the first file (Windows Store projects)
      - Updated supported for TFS based x64 projects
      - Bug fixes
      Sr. Program Manager - Multilingual App Toolkit team
    • Thank you so much!
  • Helpful tool
    2 Posts | Last post October 02, 2013
    • If you are using the Multilingual App Toolkit, you find find my new app helpful.  The XLIFF Localization Helper for Windows Phone 8 lets you open the XLF files on your phone so you can review translations on the go.  Check it out!
    • Arian,
      I love this app! Keep up the good work!