Advanced Installer now supports creating VSTO Visio Add-Ins installation projects using the Office Add-Ins wizard! This is great news for those of us who are still having to create VSTO Add-Ins, especially since Visual Studio does not include Setup & Deployment projects (again).[Read more…] about Advanced Installer now Supports Visio VSTO Add-Ins
I have written many add-ins for Visio over the years, some for private clients for use in-house, some as products for public release by my clients or by me, and some just to help me with my day-to-day Visio development tasks. The ease of installation is always an issue, and I have been using a digital certificate to guarantee its authenticity in almost all of these scenarios. I have also included licensing code from a third-party for some of my own products, but have been aware that the third-party product I have been using is not ideal because it needs its own registered component on the client machine. So, when a client asked that I use Advanced Installer to create the installation setups so that their licensing system could be used, then I was (and still am) all for it because it could become a better method for myself. However, there are some issues that I am overcoming through this transition ….not least that an apparently correctly assigned digital certificate was actually not valid.[Read more…] about Using Advanced Installer with Viso VSTO Add-Ins
I love writing Visio automation code, but I really don’t like writing setup & deployment scripts. There are so many variables : What Visio version, which edition? Which bitness (x86 or x64)? What are the user settings for the paths of stencils or templates?
So, I decided to write myself some C# functions that can be used in custom actions for an installation writing application, such as Advanced Installer. I think of the methods as being in one of three phases, Installation; Functionality and Configuration. The registry has three different areas to search within, Classes Root (HKCR); Local Machine (HKLM) and Current User (HKCU). In addition, the best way to get the true file version of Visio is to use FileInfo on the executable. The following screenshots are from a Cross-Functional Flowchart of the functions that get values for variables, and use them in other functions, until, eventually, the current user settings can be read.
[Read more…] about Reading the registry for Visio settings
Each of the functions I wrote handle the part of the registry that needs to be used. By that I mean that some settings for 64bit Visio on 64bit Windows will be in a different branch than 32bit Visio on 64bit Windows.
The first function gets the current version of the application associated with Visio drawings:
Visual Studio setup an deployment projects require the target “bitness” of target Windows operating system to be set. This means that I have to create two installation files, one for 32bit and one for 64bit Windows for my Visio add-ins, for example.
The bitness of an individual Visio application can be checked from the File / Account / About Visio dialog, and similar screens are available in other Office applications:
64bit Windows users can install either 32bit or 64bit Microsoft Office, which will install the relevant Visio Viewer package. The installed edition of Visio should then match the installed edition of Office.
Any Visio add-in installations need to match the bitness of the installed Visio application.