VSTO hosts the .NET CLR, which can execute VB.NET. But then, in order to
replicate the VBA environment, you need a friendly access to the underlying
application SDK, through ThisDocument, and so on. I believe VSTO is supposed
to provide such thing. I hope it does by the way, otherwise it means that
everyone using VBA today and willing to reuse in in VSTO in some form or
fashion will have to :
1) convert the VBA code to VB.NET (or C#) using a converter. But then expect
a lot of work, and some limitations (ActiveX support, ...)
2) use the Office Interop libraries, which are cumbersome to use to say the
least.

Hope this helps,


xlsgen, native excel generator, http://www.excelgenerator.com


"RAJ" a écrit dans le message de
...
Hi,
With the advent of .net languages.. does anyone kanow what the plans are
form Microsoft is as far as the scripting language in Excel..
Is VBA going to be replaced??