It is worth noting that VS2008 is using a very similar approach to our naming convention (in some cases, exactly the same). I think we were right to choose that approach.
The book doesn’t actually cover VSTO or VS.NET in any flavour. As a matter of fact, I haven’t even downloaded a copy of VS2008 yet.
I can also say that what I’ve witnessed of those trying to deploy Outlook add-ins crafted in using VSTO SE, I’m kind of glad we didn’t go there. Ultimately, I think to do Outlook justice you need someone who works with Outlook a great deal, and also knows their way around Visual Studio quite well. I’m not that individual.
Actually, that’s brings to mind another thing worth mentioning… We kept this strictly focussed on the “classic” Office developer, without involving any other tools that boost the cost higher than the initial Office install.
]]>Just the fact that you include a reference to all idMso and imageMso would make the book worth buying. It’s not that easy to find out the id’s of the built in commands. I know there are some Excel files to download, but still…
Do you cover anything about using VSTO and/or VS.NET 2008 to customize the ribbons? Is ribbons in Outlook inspectors covered? I have like a zillion questions about ribbon customization, so maybe I just should go out and buy the book instead……
// Johan
]]>