Localize Office add-in based on Office language pack in use

I discovered that the market value of Thread.CurrentThread.CurrentCulture was consistent to my device society, and also the really worth of Thread.CurrentThread.CurrentUICulture exemplified the Office User Interface.

I strong wind up in an instance where my Windows language is French, I don’t possess any sort of office foreign language consumer interface packs, for that cause all my menus in the Office remain in English, other than my add-in which is actually in French. It appears form of odd, so I was challenging if there’s a method to center based on existing office foreign language interface cram in use.

I’m striving to localize my office add-in, I’ve taken a look at many docs and also tutorials on techniques to do this, nonetheless they all teach on means to center it based upon precisely what the existing Windows language, not constantly precisely what office foreign language user interface pack remains in make use of.

I only support Workplace 2007 as well as Place of work 2010. It draws that our team need to check out CU and also LM home windows registry admittances for each of the varieties of the work environment, and there is actually no singular internal adjustable directing our team to the best pc computer 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.

A while back MS complex things by relabeling apps for Office (developed utilizing HTML/Javascript) to Workplace add-ins. VSTO add-ins (C#/ VB.NET) are also referred to as Workplace add-ins.

Leave a Reply

Your email address will not be published. Required fields are marked *