OWC vs Visual Studio Tools for Office

[Chinmay]

Hi,

We are currently using OWC for embedding excel and chart capabilities into
the application.

One of the issues we are facing are that the OWC components do not support
some basic functionality like Formula help, auto-completion and hints and
framework features like Undo and Redo.

One suggestion was to investigate whether the Visual Studio for Office
toolset can support those features and replace the OWC components.

Wondering how the experts on this newsgroup feel about that.

Thanks,
Chinmay

 

[Alvin Bruney - MVP ASP.NET]

some basic functionality like Formula help
not true. help docs are internally supported and readily available.

, auto-completion and hints and true
framework features like Undo and Redo.

not true. this is fully supported

VSTO does offer advantages that aren't available in OWC such as embeddable
objects in the document surface and bona-fide scalablility for server-side
implementations. Outside of these two logical groups, the playing field is
even. Remember, these two approaches target the same underlying platform.

A couple serious disadvantages to VSTO is that it requires the .NET
framework on the client machine. Interactive office components that run in a
web browser is not supported.

Consider your target audience and then make a decision.

--
Regards,
Alvin Bruney

Shameless Author Plug
[The Microsoft Office Web Components Black Book with .NET]
www.lulu.com/owc, Amazon, Barnes & Noble etc
Forth-coming VSTO.NET