Localizing a .NET office extension (desktop)

This article summarizes my experience on translating office add-ins to multiple language. It is not an official guide, but just how you could do it. It assumes you have an office extension (VSTO, desktop) in a single language, and want to provide it in some other languages for users in other countries. GitHub demo repository: https://github.com/nbelyh/VstoMultiLanguageDemo For generic information on localization on application localization in .NET, please refer the official Microsoft documentation: https://docs.microsoft.com/en-us/dotnet/framework/resources/index The steps I suggest:

Introducing IdMso visual studio extension

A few months ago I released a visual studio extension, that provides autocomplete if you edit¬†office ribbon files. The extension is open source, and published on GitHub. By now, it proved to be more of less functional and even some issues with Office 2016 icons were fixed thanks to the user feedback! ūüôā What it can do for you – it can assist you if you edit the XML files to define¬†interface for your extensions in the Visual Studio editor. The code is based on famous glyphfriend¬†extension (if you don’t use it yet – you should start, it’s great). Initially …