To localize your COM add-in, you need to know the language settings of the Office application (host application) that the add-in is currently loaded in. In this post you will find some VB.NET and Delphi code samples of localizing your COM add-ins.
To make your controls look like Office ones isn’t a simple task. When Office developers show .NET controls in their add-ins or standalone applications, they have to customize controls in order to conform to Office color styles.
Why the Ribbon tab designer by Add-in Express is better than that of VSTO 2008? Because it prevents the Office 2007 Ribbon XML from being constructed manually and in this way leaves no place for run-time errors.
How to get started with COM add-ins for Microsoft Office 2007 - 2000. Learn about object models, typical issues with Office add-ins, add-in deployment, shims, ClickOnce and more.
Special components for Office 2000 - 2007 customization. Customize the Office UI including toolbars, menus, sub-menus, ribbons, task panes and property pages.
Security and deployment, RAD modules and visual designers for Microsoft Office plug-ins. Adding toolbars, customizing Office Ribbon, Quick Access toolbar and Office Menu, creating task panes and more.
Create secure, deployable, version-independent Microsoft Office extensions on RO Chrome for Visual Studio. Use RAD modules, designers and components to develop application-level COM add-ins, smart tags, RTD servers and user-defined functions.
Moving your add-in projects from C++ shims to Add-in Express .NET Loader. Get your add-in registered in the host application automatically.
How Add-in Express .NET integrates MS Office PIAs into add-in solutions. Strategy and tactics of using MS Office PIAs. And about benefits of late binding.
Office Primary Interop Assemblies. The official opinion of Microsoft. Is it possible to create an add-in with PIAs for all Office versions?
Here I will show you what is included in Add-in Express solutions. Attention, GUIDs are everywhere! Also I will speak about things that can be added to the add-in project, and tell you what should be done to retire right now.
What are the shims and is it necessary to sign add-in projects with strong names? In general, I strongly recommend always including shims in your add-in projects if you have C++ in your Visual Studio .NET.
Why doesn’t Add-in Express .NET for Visual Studio 2005 support the automatic generation of setup projects? And is it possible to develop add-ins on Visual Studio 2003 and Visual Studio 2005 on one computer?
