Just to give you some backgroud info, I'm trying to automation excel from c#
..NET.
I need to be able to export to excel 2000, 2002, 2003. I will install
excel 2000 and then reference the assembly generated using "TlbImp Excel9.olb
Excel.dll" in my c# .NET code.
Once I reference the generated assembly, I'm assuming that I can create
objects using early binding? Is this true?
Also, should the interop assembly I generate for excel 2000 work with excel
2002 and 2003?
Thanks.
Mansi
[quoted text, click to view] "Mattias Sjögren" wrote:
>
> >It's mentioned in one of the posts that you can use Excel09.obj to create a
> >dll using
> >TlbImp Excel9.olb Excel.dll., but what are the steps to do this?
>
> That should be the only step required. After that you just reference
> the generated assembly.
>
>
>
> Mattias
>
> --
> Mattias Sjögren [MVP] mattias @ mvps.org
>
http://www.msjogren.net/dotnet/ |
http://www.dotnetinterop.com > Please reply only to the newsgroup.
For the most part, typelibs (or rather, their implementations) are
backward compatible. COM guidelines dictate that you don't change
managed interface (instead you derive new ones), CLSIDs stay the same,
etc. With Office, these rarely change. As long as the 2000
implementations suit you they should be supported in most cases in 2002
and 2003.
--
Heath Stewart
Software Design Engineer
Developer Division Sustained Engineering
Thanks for the info.
I know this next question should be posted in another discusssion group, but
I need to be able to export a picture/image file from c# to excel. Is there
any way to do this?
Mansi
[quoted text, click to view] "Heath Stewart [MSFT]" wrote:
> For the most part, typelibs (or rather, their implementations) are
> backward compatible. COM guidelines dictate that you don't change
> managed interface (instead you derive new ones), CLSIDs stay the same,
> etc. With Office, these rarely change. As long as the 2000
> implementations suit you they should be supported in most cases in 2002
> and 2003.
>
> --
>
> Heath Stewart
> Software Design Engineer
> Developer Division Sustained Engineering
> Microsoft Corporation
Don't see what you're looking for? Try a search.