Building Office System .NET Assemblies
Having ‘stabilized’ the VBA version of Clean XHTML, the assumption here is that a design is achieved that can be translated into C# Office Interop. Why C#? Because I just want to make my life more difficult to enjoy. Am I being sarcastic? Of course I am—and, of course, VB.NET is easier to use (really) as of the current released version of VSTO but I chose C# because VB.NET does not ‘natively’ support self-documentation. Yes, there is VBCommenter but (sigh)…
So, before the next move is made to translate the new VBA discoveries into a VSTO build, there is a need to review the findings collected during the first pass sketch laid out in VSTO. So to back track for the confused: I started Clean XHTML before Office 2003 came out in VSTO. Then Office 2003 came out—so I was ‘moved’ to write a VBA version (several hundred lines of code used for crazy research purposes only). Now is the time to merge the VSTO stuff with the VBA stuff—and pray that what works in native VBA will work in Interop (because on-the-ground experience with VSTO shows that there are no guarantees—especially when using C#).
These findings are flippantly thrown into the Funky Knowledge base in “Visual Studio Tools for Office: Flippant Remarks about Office System Word VSTO 1.x Projects” at SonghaySystem.com.