Localizing a .NET office extension (desktop)

This article summarizes my experience on translating office add-in to multiple language. It is not an official guide, but just how you could do it. It assumes you have an office extension (VSTO, desktop) in a single language, and want to provide it in some other languages for users in …

Using SolutionXML with C#

Visio has a feature which allows third-party solutions to store it’s custom data in Visio files as XML fragments. It might be useful if you don’t want to litter document or shapes shapesheet(s) with your data. Also it has an advantage that setting it, unlike setting cells in shapesheet, does …

Visio project templates updated (Visio 2016, VS 2015 support)

Visio project templates updated to version 1.0.7: – added support for Visual Studio 2015 – added support for Visio 2016 – Simplified source code (removed extra files, so that project structure is more like vanilla VS). – Unified project wizard. Now there is one wizard to rule it all. It …

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 …

Persisting Visio shapes

This article explains this post in microsoft.public.visio.developers newsgroup, and provides information on how one can to save Visio shapes in external source exactly, so here is the code to store master/shape in a stream and then drop it back to the document: To save Visio shapes in some external system (persist …