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 …

Using the same set of button images with transparency in all Visio versions

If you write a Visio add-in that targets multiple Visio versions at the same time, and have some custom buttons with images (with transparency), you might run into trouble with that new Visio 2010 Ribbon user interface needs different “flavor” of images compared to Visio 2003 and 2007. So you’ll have to to either create two separate sets of images (one set for pre-ribbon version of Visio, the second set for the ribbon one), or to “dance around a little” and make both versions consume the same set of images. The article focuses on the second approach I ended up …

Making the Visio ribbon tab document-dependent

This post explains how to make a ribbon tab in Visio 2010 ribbon document-specific. Means, activate a custom ribbon tab only for a specific document. This article discusses the implementation of a document-specific tab in a COM add-in; also, it focuses on details you might be interested in if you e.g. program unmanaged C++. Note that you could create a custom document-specific ribbon by other means, e.g. by embedding your custom interface in a document template using new Visio 2010 property Document.CustomUI Nevertheless, one of the ways to it is