![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
![]()
I am working on an Outlook add-in that has custom forms and interacts
with web services. The current version is a managed (C#.net) COM add- in, but I am running into a number of issues, most involving other add- ins. I'm looking into two possible solutions: using a COM shim and using VSTO. My understanding is that with a COM shim, there is minimal rewrite of existing code, but that VSTO would allow me to use managed code. I am required to have only one codebase for both Outlook 2003 and 2007 (and possibly future versions). Any advice would be greatly appreciated. |
#2
|
|||
|
|||
![]()
Hi Joe,
I am working on an Outlook add-in that has custom forms and interacts with web services. The current version is a managed (C#.net) COM add- in, but I am running into a number of issues, most involving other add- ins. I'm looking into two possible solutions: using a COM shim and using VSTO. My understanding is that with a COM shim, there is minimal rewrite of existing code, but that VSTO would allow me to use managed code. I am required to have only one codebase for both Outlook 2003 and 2007 (and possibly future versions). Any advice would be greatly appreciated. I made the decision a while ago to use C++ to write a COM addin natively. You have all the control you need and no unsolveable problems to integrate in all Office versions from one addin. So if you have enough knowledge on C++ and COM, it is worth consideration. -- SvenC |
#3
|
|||
|
|||
![]()
Both VSTO and shared, shimmed addins are managed code and can be written in
C#. It's much harder if not impossible to support both Outlook 2003 and 2007 in a VSTO addin unless you decide not to support the ribbon in Outlook 2007. There are workarounds for using the ribbon in shared addins even when compiled as Outlook 2003 addins. If using managed code and a shared addin you definitely should shim it to give it it's own AppDomain so crashes or problems in other addins don't get yours disabled. -- Ken Slovak [MVP - Outlook] http://www.slovaktech.com Author: Professional Programming Outlook 2007 Reminder Manager, Extended Reminders, Attachment Options http://www.slovaktech.com/products.htm "Joe Lakey" wrote in message ... I am working on an Outlook add-in that has custom forms and interacts with web services. The current version is a managed (C#.net) COM add- in, but I am running into a number of issues, most involving other add- ins. I'm looking into two possible solutions: using a COM shim and using VSTO. My understanding is that with a COM shim, there is minimal rewrite of existing code, but that VSTO would allow me to use managed code. I am required to have only one codebase for both Outlook 2003 and 2007 (and possibly future versions). Any advice would be greatly appreciated. |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
deploy 2003 vsto addin on outlook 2007 problem | lokesh | Add-ins for Outlook | 17 | April 17th 08 04:36 PM |
Upgraded Outlook to 2007, now VSTO doesn't work | HÃ¥kan | Outlook and VBA | 1 | August 28th 07 02:19 PM |
VSTO 2005 SE add-in for Outlook 2003 & Outlook 2007? | Michael | Add-ins for Outlook | 3 | January 23rd 07 08:16 PM |
Outlook 2007 Add-in using VSTO 2005 SE | Kenn | Outlook - Using Forms | 1 | November 4th 06 03:27 AM |
VSTO Backwards compatibility with Outlook 2003 / 2007 | abcomp | Add-ins for Outlook | 1 | July 19th 06 04:14 PM |