A
Alan
Hi
We've been developing Outlook components for several years. These include
Exchange client extensions, COM Add-ins and Service Providers, all written
in C++. In line with Microsoft our client extensions have virtually
disappeared, and most code is now in the COM Add-in; but with having to
support Outlook 2007, is now the time to move over to C#?
Looking at Outlook 2007 and all of the new features (in particular Ribbon
Bar and Form Regions) it seems that most (if not all) examples are provided
in C# (or VB.net, which I'm not considering). My experimenting with C# tell
me it is quick and easy, but what happens if I have to dive into MAPI from
my new C# code (as was often the case in earlier version of our COM Addin).
Any thoughts, experiences are much appreaciated.
Alan.
We've been developing Outlook components for several years. These include
Exchange client extensions, COM Add-ins and Service Providers, all written
in C++. In line with Microsoft our client extensions have virtually
disappeared, and most code is now in the COM Add-in; but with having to
support Outlook 2007, is now the time to move over to C#?
Looking at Outlook 2007 and all of the new features (in particular Ribbon
Bar and Form Regions) it seems that most (if not all) examples are provided
in C# (or VB.net, which I'm not considering). My experimenting with C# tell
me it is quick and easy, but what happens if I have to dive into MAPI from
my new C# code (as was often the case in earlier version of our COM Addin).
Any thoughts, experiences are much appreaciated.
Alan.