I’m back from the Microsoft Tech Day / Community Day 2012 at Madrid, which have been great. The aspect that I like most is networking with people, either old MVPs that I already know, new MVPs or other people.
In this event I was introduced to Jesús Salas, the author of VS Anywhere, also available on the Visual Studio Gallery, an extension for Visual Studio that provides team collaboration in real time with a very innovative approach.
I also met my friend Pep Lluis Baños, Visual Basic MVP like me, who brought to the event an intriguing kind of electronic mini motherboard that happened to be the mainboards used in .NET Micro Framework, a technology that I only knew the name. Since I returned, I have been so excited about this technology that I have watched the Gadgeteering and the .NET Micro Framework video, I have read documentation, I have bought the Getting Started with .NET Gadgeteer book that I am reading and I do plan to buy some .NET Gadgeteer Starter Kit for Christmas to start playing. It’s great also to see how powerful and flexible Visual Studio and the .NET Framework have become to accommodate all kind of extensions with project types, visual designers for electronic layouts, debuggers with external devices, etc.
In the past years, I have received some bug reports (less than 10 out of dozens of thousands of installations) reporting that the setup of MZ-Tools 3.0 for VBA / VB6 was failing with this error:
“Unable to register DLL/OCX:RegSvr32 failed with exit code 0x5”
I never discovered the cause (I just recommended to reinstall Office or VB6, depending on the case, or I sent the list of dependencies), but in the last weeks the problem has happened to two users of Microsoft Office 2013 using a clean installation. I already suspected that the problem was related to the file MSADDNDR.DLL (in the folder C:Program Files (x86)Common Filesdesigner), the reference used by add-ins for VB6 and for the VBA editor.
So I decided to investigate, and lo and behold, it happens that Office 2013 doesn’t install that file, it just installs the MSADDNDR.OLB object library file. I even used the orca.exe tool of the Microsoft Windows SDK to open the .msi files of the Office 2013 setup to verify. I guess that somehow some users of VB6 and old versions of Office had this file missing or damaged, what would explain the case completely.
To fix the problem, the new setups of MZ-Tools 3.0 released today install this file:
MZ-Tools 3.0.1206 for VBA with bug fix to support Microsoft Office 2013