"Nolan Johnson via .NET 247" <anonymous@dotnet247.com> wrote in message
news:OP1rM3sYFHA.1344@TK2MSFTNGP15.phx.gbl...
> Newbie question. I see lots of details about how to use COM to create and
> manipulate Excel objects from c# here and elsewhere on the web.
>
> We're going to re-work a VBA application that we have that does some
> complex manipulations of Excel files, and one thing that we're considering
> is c# or VB and COM rather than VBA.
>
> The question is this: can I do absolutely everything in c#/COM that I
> could do in VBA? Or are there limitations? I want to make sure that I
> won't lose any functionality before committing to any particular toolset.
>
> Thanks.
>
> --------------------------------
> From: Nolan Johnson
>
> -----------------------
> Posted by a user from .NET 247 (http://www.dotnet247.com/)
>
> <Id>R0uaKKbxYUmref8NQMAjAA==</Id>

"Peter Jausovec" <peter[at]jausovec[dot]net> wrote in message
news:uAr$AQtYFHA.1152@tk2msftngp13.phx.gbl...
> Hi,
>
> Did you consider using VSTO ?
>
> Regards,
> Peter Jausovec
> (http://blog.jausovec.net)
> "Nolan Johnson via .NET 247" <anonymous@dotnet247.com> wrote in message
> news:OP1rM3sYFHA.1344@TK2MSFTNGP15.phx.gbl...
>> Newbie question. I see lots of details about how to use COM to create
>> and manipulate Excel objects from c# here and elsewhere on the web.
>>
>> We're going to re-work a VBA application that we have that does some
>> complex manipulations of Excel files, and one thing that we're
>> considering is c# or VB and COM rather than VBA.
>>
>> The question is this: can I do absolutely everything in c#/COM that I
>> could do in VBA? Or are there limitations? I want to make sure that I
>> won't lose any functionality before committing to any particular toolset.
>>
>> Thanks.
>>
>> --------------------------------
>> From: Nolan Johnson
>>
>> -----------------------
>> Posted by a user from .NET 247 (http://www.dotnet247.com/)
>>
>> <Id>R0uaKKbxYUmref8NQMAjAA==</Id>
>
>

"Joe Schmoe" <nobody@here.com> wrote in message
news:af0Se.12865$tT.5738@okepread02...
> What does that get anyone? Took a quick look and it looks like it's still
> just a bunch of slow Interop calls, possibly made slower because VSTO just
> wraps the Interop calls. Just really didn't get the point of using VSTO.
>
> I'd like to find a pure .NET way of generating Excel (or other Office)
> files. Interop is too slow when doing things that will need thousands of
> calls.
>
> Please educate me if you know. :)
>
> "Peter Jausovec" <peter[at]jausovec[dot]net> wrote in message
> news:uAr$AQtYFHA.1152@tk2msftngp13.phx.gbl...
>> Hi,
>>
>> Did you consider using VSTO ?
>>
>> Regards,
>> Peter Jausovec
>> (http://blog.jausovec.net)
>> "Nolan Johnson via .NET 247" <anonymous@dotnet247.com> wrote in message
>> news:OP1rM3sYFHA.1344@TK2MSFTNGP15.phx.gbl...
>>> Newbie question. I see lots of details about how to use COM to create
>>> and manipulate Excel objects from c# here and elsewhere on the web.
>>>
>>> We're going to re-work a VBA application that we have that does some
>>> complex manipulations of Excel files, and one thing that we're
>>> considering is c# or VB and COM rather than VBA.
>>>
>>> The question is this: can I do absolutely everything in c#/COM that I
>>> could do in VBA? Or are there limitations? I want to make sure that I
>>> won't lose any functionality before committing to any particular
>>> toolset.
>>>
>>> Thanks.
>>>
>>> --------------------------------
>>> From: Nolan Johnson
>>>
>>> -----------------------
>>> Posted by a user from .NET 247 (http://www.dotnet247.com/)
>>>
>>> <Id>R0uaKKbxYUmref8NQMAjAA==</Id>
>>
>>
>
>