Excel Add-Ins without VSTO

[CybearInsight]

I'm using Dyalog APL, a .Net language which is strong on numerical analysis
of multi-dimensional array. The product only supports "loose" integration
with VS - so I don't believe VSTO is an option for me. I'm looking for
documentation on types of add-ins that I will be able to write for Excel
using this kind of tool. I'm hoping that "all I need to do" is generate an
assembly containing a class which either derives from a suitable "add in"
base class or supports some relevant interfaces.

If this is possible, can anyone point me at documentation which describes
how to do this (which classes/interfaces), ideally with some examples?

 

[NickHK]

These NGs may be more appropriate :
microsoft.public.excel.interopoledde
microsoft.public.excel.sdk

NickHK

 

[Peter Huang [MSFT]]

Hi,

The Excel Addin is a COM based technology.
Any COM supported language can implement the Addin interface, so we can use
VB/VC/C# ..... to generate an Excel COM Addin.

But as for Dyalog APL, I did not know that before, so I am not sure if it
is a COM Ready programming.

So in addition to Nick's suggestion, you may also consult the Dyalog APL
related resource.

Thanks!


Best regards,

Peter Huang

Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[CybearInsight]

Thanks,

Dyalog APL is COM "Ready" (if that is the right word in 2006), but I was
hoping to use .NET. I see that I forgot to mention that I am targeting Excel
2007. Surely(!?) Office 2007 has a (several?) .NET based mechanism(s) for
implementing extensions?

Morten

 

[NickHK]

Nothing I have read about Office 2007 indicates that MS is moving it towards
the .Net side ; only VBA internally supported, with COM.
But it seems MS are providing more tools/means to work with Office app from
the .Net languages, although that is nothing to do Office per se.

NickHK

 

[Peter Huang [MSFT]]

Hi Morten,

I agree with Nick's idea.
In nature the Office is still COM based, but in Office 2007 we have wrapped
the COM interface.
e.g.
In Excel 2003, if we want to write addin for Excel, we have to use PIA(
which is a .NET wrapper for office interface), and after we write class
library to implement COM Addin interface and register it to COM
In Excel 2007, We have more choice, e.g. application level Addin which did
not need register to COM, but this is because we make more efforts to use
VSTO to help load the .NET assembly and interactive with Office
application.(but it seems that you did not want VSTO).

Also since office 2007 is still in beta release, as for the development on
beta product you may try to post in the forum below.
Visual Studio Tools for Office
Questions on using Visual Studio 2005 Tools for the Microsoft Office System
to create managed code solutions in Excel 2003, Word 2003, InfoPath 2003, &
Outlook 2003
http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=16&SiteID=1

If you have any concern, please feel free to let me know.

Best regards,

Peter Huang

Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.