MS Office and .NET framework

[Elephant]

Helllo,

is there a version of Microsoft Office, where you can link .NET Dll's (
assemblies ) with it, instead of COM Dll's? If not, does anybody know when
there will be?

Thank you for any info,

Me.

[Bryan]

There is no version of Office at present that exposes a .Net interface to
its object model, but Microsoft has primary interop assemblies available for
calling Office objects via COM from .Net. But unfortunately it has to go
thru the COM Interop and the marshalling can be painfully slow if you are
transferring large amounts of data.

In our project we have basically implemented an Excel XLA addin to help make
the communication with .Net "chunky" rather than "chatty" so that the
performance hit is kept to a minimum. There are numerous articles on
designing of "chunky" vs "chatty" interfaces to help with the COM interop
issues on MSDN.

If I had to guess, I would say that a version of office that is pure .Net is
still a good distance away, but I'm really really hoping that Microsoft
releases an interface that does a much more efficient job marshalling the
data.
"Elephant" <el******@microsoft.com> wrote in message
news:TJ********************@casema.nl...

Helllo,

is there a version of Microsoft Office, where you can link .NET Dll's (
assemblies ) with it, instead of COM Dll's? If not, does anybody know when
there will be?

Thank you for any info,

Me.

[Gerry Hickman]

Bryan wrote:

There is no version of Office at present that exposes a .Net interface to
its object model,

??

What's the score with Office 2003? What is the "official" way to program
it, surely it can't be VBA??

--
Gerry Hickman (London UK)

[Bryan]

"Gerry Hickman" <ge********@yahoo.co.uk> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...

Bryan wrote:

There is no version of Office at present that exposes a .Net interface to
its object model,
??

What's the score with Office 2003? What is the "official" way to program
it, surely it can't be VBA??

You can code it with VBA, or thru external automation - but all the
interfaces are still COM. The only way to code it thru .Net is to use the
interop.

Bryan

--
Gerry Hickman (London UK)

[Gerry Hickman]

Bryan wrote:

What's the score with Office 2003? What is the "official" way to program
it, surely it can't be VBA??

You can code it with VBA, or thru external automation - but all the
interfaces are still COM. The only way to code it thru .Net is to use the
interop.

Doesn't exactly inspire confidence if Microsoft's flagship product does
not directly support .NET

Was there not something called VSA that was going to enable office apps
to work direct with .NET?

--
Gerry Hickman (London UK)