Add-On <-> COM Add-In ?

[SomeNewDev]

Hi,

I'm not new to developing, but kinda new to Office automation.
I already know this comparison between Add-On and COM Add-In:
http://msdn.microsoft.com/de-de/library/bb851468(en-us).aspx

My question is, is there a not mentioned 'important' difference them ?

Google only gives me ".. in the end it's just a 20% speed advantage for
Add-ons, nothing more !".

Is there anybody who has more experience with this ?

I just wanna know, if e.g I will start to code an Add-In in C#,
that I won't miss a single 'possibility' in the future.
On the other side, why should I bother myself with C++, if
it won't give me a single advantage at all (inspite of slightly faster
performance) ?

Thank you..

 

[David Parker]

... don't forget the new .Net 3.5 Add-ins in VS 2008 :
http://msdn.microsoft.com/en-us/magazine/cc163476.aspx
http://blogs.microsoft.co.il/blogs/bursteg/archive/2007/08/13/Build-AddIns-with-System-AddIn.aspx

A lot of the problems is with deployment. Check out Chris Castillo's video
in the Developer track at:
http://blogs.msdn.com/visio/archive/2008/05/21/visio-conference-2008-videos-posted.aspx

 

[SomeNewDev]

Thanks a lot for the links ! They somewhat harden the sense of using dotNET.

Don't get me wrong, I would try to avoid naked C or C++ anyway.
I was just curious, if anybody knows of a case when using ->native<- code
might be a must-have or at least a great win concerning visio add-in
development.

For instance there's still C++/CLI. As far as I can see, I would be on the
safe side with it, but imo would be too laborious to code in.