Beauty comes from within. This is true with add-ins as much as it is true with people. But with add-ins, there is a greater need to advertise their beauty via a customized user interface. Without a nice UI, the user might never 1) notice your add-in’s existence and 2) initiate any of the add-in’s beautiful features.
A popular user interface customization is custom ribbons and custom toolbars. I think you know what these are and we’ll cover how to create both of them for Microsoft Word.
We’ll start with Ribbon and work our way back to the legacy toolbars (aka CommandBars).
- Creating custom ribbons for Word 2013 – 2007
- Creating custom toolbars for Word 2003
There are three main scenarios for custom ribbons. They are:
- Create a new ribbon: adds an additional tab to the Word Ribbon.
- Customize an existing Word ribbon: your customizations integrate with an existing tab.
- Create a context-sensitive one: the custom ribbon tab only displays when a specific context is active (e.g. editing headers and footers in a Word document).
Mastering these three scenarios covers Pareto Principle and will make you appear like a Word UI customization master. Add some experience and you will be. Let’s take the scenarios one-by-one.
I think this is the most common type of customization. I don’t have a large sample of developers to back me up. It’s just my preference. I think it is typically less confusing to the user because the new ribbon tab is conspicuous. It’s easy for my users to notice and find the Word addin’s commands.
Let’s build a tab like the one I showed in my last article: Customizing Word User Interface.
Before we begin, you need to:
- Open Visual Studio 2012.
- Create a new ADX COM Add-in project using Add-in Express for Office and .net.
- Choose your preferred language (I went with VB.NET, you can use C# or C++.NET as well).
- Select Office 2003 as the minimum supported Office version.
- Select Word (and only Word) as the supported application.
After you create the project, you can crank out an attractive custom ribbon for Microsoft Word 2007, 2010 and 2013 in just a few minutes by completing these steps:
- Open the AddinModule in design view. Add a new tab (ADXRibbonTab) to it. Set the following properties for the tab:
- Caption=MY RIBBON TAB
- Add an ImageList control to the AddinModule. It will contain the icons for the ribbon buttons. Leave the name as is but set its ImageSize=32,32. Then add two icons you like to the Images collection. Just make sure the icons are 32 pixels by 32 pixels.
- Select the CustomRibbon and use the visual designer to add the following controls and set their properties according the table below
|Control||Parent||Properties & Values|
|ADXRibbonGroup||CustomRibbon||Caption=Custom Action Group|
|ADXRibbonSplitButton1||AdxRibbonGroup1||Caption=Create Doc from Template
|ADXRibbonButton||ADXRibbonMenu1||Caption=Technical Design Document|
|ADXRibbonCheckBox||AdxRibbonGroup1||Caption=Auto-check for new Templates?|
After completing, your custom Word ribbon should look similar to this:
This ribbon will display to the far right of all Word ribbon tabs. But what if you don’t want to display it there? What if you want it to display just to the right of the HOME tab… loud and proud?
Well, it’s both easy and simple to do. Just select the CustomTab in the designer. Then configure its InsertAfterIdMso property to TabHome.
All of the ribbon controls have a control ID. Microsoft provides a nice set of control ID reference docs to help us out.
You can utilize the InsertBeforeIdMso property to position the custom tab.
Sometimes it is better to integrate a custom ribbon within an existing one. This is best when your features closely relate to existing ribbon commands. It’s also appropriate when you want to override a standard Word ribbon button’s feature.
Let’s take our custom ribbon and make the following changes to it:
- Select the CustomRibbon on the AddinModule.
- Change its IdMso property to TabHome.
- Select the AdxRibbonGroup1 control (Custom Action Group) in the ribbon designer.
- Change its InsertBeforeIdMso property to GroupClipboard. This will cause the group to display as the first group in the HOME tab.
If you are adding features that should only display in certain contexts, this is the type of ribbon to build. A good example of a context sensitive ribbon is the image editing or table editing ribbons. These ribbons display when you select an image or table respectively. They provide the commands needed to edit them as you see fit.
To make the CustomRibbon display only within a specific Word context just change its Context property.
By setting this property, you tell Office to only display the custom ribbon in this specified context.
Thus, Microsoft Word does not display them when they are not the current selection.
Toolbars, also known as CommandBars, are long gone if your solutions only support Office 2007 – Office 2013 (yes, I know Outlook 2007 makes limited use of them). I’ll let you do that if you prefer. But, just know you are significantly reducing your potential user base if you ignore Office 2003 and earlier.
Using Add-in Express, it is easy to support toolbars and ribbons in the same project. This greatly reduces your development & maintenance efforts because you only need single code base for all version of Office 2003 through 2013. Let’s look at how to create custom Word toolbars.
Similar to a ribbon, we can create custom toolbars that fit our needs. They display as a row of controls in a separate “strip” called a CommandBar (users call them a toolbar).
With Add-in Express, we add an ADXCommandBar control the AddinModule and set the following properties:
- CommandBarName = My Custom Toolbar
- SupportedApps = Word
Now add some controls to the CustomToolbar according to the table below:
|Control||Parent||Properties & Values|
Technical Design Document
|AdxCommandBarButton||CustomToolbar||Caption=Create from Template
|CheckBox||AddinModule||Caption= Auto-check for new templates?|
|ADXCommandBarAdvancedControl||CustomToolbar||Control = Label1|
|ADXCommandBarAdvancedControl||CustomToolbar||Control = CheckBox1|
The last three controls are exclusive to Add-in Express. They allow you to host .NET controls in the Office toolbar… something not supported by Visual Studio out-of-box.
By utilizing these controls, I’m able to host a label and checkbox on the custom toolbar. Thus, the toolbar can closely mimic the design of the ribbon.
You change the toolbar to integrate with an existing toolbar. All you need to do is know the name of the target toolbar and set it as the value of the CommandBarName property. I recommend using our Built-In Controls Scanner (a free utility) to help find the name of the Office 2003 and earlier toolbar and control IDs.
Here, I’ve changed the toolbar to display in Word 2003′s standard toolbar:
Note. The advanced controls do not function when you integrate with a standard Word toolbar. Thus, you need to remove both of the ADXCommandBarAdvancedControl objects for this integration to work.
If you delete the controls, then, at runtime, your custom Word toolbar integrates with the standard toolbar and looks like this:
Sometimes, I miss the old toolbars. Their elegance is their simplicity.
That’s all there is to it. We make it easy to build custom Word ribbons and toolbars. Unfortunately, its up to you ine the requirements of your users. That’s not so easy.
This sample Word addin was developed using Add-in Express for Office and .net:
Word add-in development in Visual Studio for beginners:
- Part 1: Word add-in development – Application and base objects
- Part 2: Customizing Word UI – What is and isn’t customizable
- Part 3: Customizing Word main menu, context menus and Backstage view
- Part 5: Building custom task panes for Word 2013 – 2003
- Part 6: Working with Word document content objects
- Part 7: Working with Word document designs, styles and printing
- Part 8: Working with multiple Microsoft Word documents
- Part 9: Using custom XML parts in Word add-ins
- Part 10: Working with Word document properties, bookmarks, content controls and quick parts
- Part 11: Populating Word documents with data from external sources
- Part 12: Working with Microsoft Word templates