I’m aiming to localize my workplace add-in, I’ve checked out many docs and tutorials on ways to do this, however they all teach on ways to localize it based on exactly what the current Windows language, not always exactly what office language interface pack is in use.
So I wind up in a scenario where my Windows language is French, I don’t have any office language user interface packs, for that reason all my menus in the Office remain in English, other than my add-in which is in French. It looks type of odd, so I was questioning if there’s a method to localize based on existing office language user interface pack in usage.
I discovered that the value of Thread.CurrentThread.CurrentCulture corresponded to my system culture, and the worth of Thread.CurrentThread.CurrentUICulture represented the Office UI.
I just support Workplace 2007 and Workplace 2010. It draws that we have to look at CU and LM windows registry entries for each of the variations of the workplace, and there is no single internal variable pointing us to the right pc registry course.
There is a MSDN page on Loading Resources Based on Workplace User Interface Language. It’s utilizing the LanguageSettings from the Application object to figure out the existing language of the Workplace UI.
The Windows Shop was created for setting up applications that would run in personal sandboxes that would keep apps separated (in case of concerns) from your operating system and other applications. However, Desktop applications frequently have computer registry entries, dll reliances, and other client-side requirements. Due To The Fact That the Windows Store can not accommodate these OS-related and client-side requirements, desktop applications can not presently be dispersed through the Windows Shop
Luckily, Microsoft is finally addressing this problem. They are in the process of completing Task Centennial, which will allow one to transform desktop apps for distribution through the Windows Store. It does this by providing a different computer registry for desktop apps and a method for dlls to operate without injuring other applications.
Since this writing, Microsoft has withdrawn the preview variation of their Task Centennial Desktop App Converter. I am hoping this remains in preparation for releasing a stable variation.
Will Job Centennial allow VSTO add-ins to be sold via the Windows Store? I am confident, but this is not particular. We must understand more within the next few months, if not faster.