Re: Future of VBA
Nick Hodge
has been supported right up to current versions, so for over 15 years since
it was developed. Of course it hasn't been updated since VBA was introduced
in V5.
MS are putting a lot of 'effort' into VSTO (Visual Studio Tools for Office)
to use Office objects under .NET languages, but it has a long way to go to
get volume use, as many people develop with VBA and apart from security and
distribution, there is little that cannot be done easier and directly in
VBA.
For sure VBA will be around for some product iterations yet. If you want to
be more future proof I suspect VSTO is the way to go. If you are thinking of
major projects now, VBA will be around and supported for long enough to
satisfy the lifecycle of any application built with it.
Just my Ł0.02
--
HTH
Nick Hodge
Microsoft MVP - Excel
Southampton, England
nick_hodge...@zen.co.uk.ANDTHIS
"Sean" <Se...@discussions.microsoft.com> wrote in message
news:2F76E9BE-7C27-4EA8...@microsoft.com...
> Looking for some solid information about the future of VBA.
> Will MS create a .Net version of VBA for its office products? phase it out
> completely? if so whats the lifecycle? etc.
Sean
concerns if I am going to take VBA deeply. VBA is a great thing to know for a
wow factor and to help a small company with an IT problem but I have been
concerned about protecting my work and also issues of installation which is
what I assumed the Office "developer" edition address which it seems MS is no
longer making Office "developer" and going VS instead.
I see VBA like javascript. Fun, quick, simple, fast, totally insecure. While
serious solutions should be done on ASP most likely serious solutions for
Office should be done in VS
"Nick Hodge" wrote:
> You'll not get any answers that are based on fact. The Excel macro language
> has been supported right up to current versions, so for over 15 years since
> it was developed. Of course it hasn't been updated since VBA was introduced
> in V5.
>
> MS are putting a lot of 'effort' into VSTO (Visual Studio Tools for Office)
> to use Office objects under .NET languages, but it has a long way to go to
> get volume use, as many people develop with VBA and apart from security and
> distribution, there is little that cannot be done easier and directly in
> VBA.
>
> For sure VBA will be around for some product iterations yet. If you want to
> be more future proof I suspect VSTO is the way to go. If you are thinking of
> major projects now, VBA will be around and supported for long enough to
> satisfy the lifecycle of any application built with it.
>
> Just my £0.02
Howard Kaikow
Protecting code is far more important than the benefits of using Windows
Forms, etc.
Not to mention being able to write VBA that works in Office 97 and later.
Charles Maxson
MSFT is keeping one current to Office (VBA) thru each release while building
on the other one (VSTO), which gives developers a choice. Both of these have
their merits and of course weaknesses, so it can often be an application by
application decision on which to use when. If VBA (VB6) does it for you,
stay there. Like Nick said, it is so tightly integrated its hard to ignore
how well it works.
If you can take advantage of the innovation in VSTO 2005 and the initial
deployment is not a barrier, its worth a consideration. You can do a lot
more with it than VBA but the bar is a bit higher for entry.
.... either way, you can get alot down by automating Office and you have
choices .... and time.... I would imagine MSFT will support VBA for a quite
a long time to come. Case in point, XLM Excel 4.0 macros still are kickin'
and they were not fractionally as widespread as VBA. Its likely all of us
will still be banging out some VBA in the years to come...
Charles
www.officezealot.com
"Howard Kaikow" <kai...@standards.com> wrote in message
news:ux5YU06U...@tk2msftngp13.phx.gbl...
Leviatano
Leviatano
Leviatano
"Nick Hodge" wrote:
> You'll not get any answers that are based on fact. The Excel macro language
> has been supported right up to current versions, so for over 15 years since
> it was developed. Of course it hasn't been updated since VBA was introduced
> in V5.
>
> MS are putting a lot of 'effort' into VSTO (Visual Studio Tools for Office)
> to use Office objects under .NET languages, but it has a long way to go to
> get volume use, as many people develop with VBA and apart from security and
> distribution, there is little that cannot be done easier and directly in
> VBA.
>
> For sure VBA will be around for some product iterations yet. If you want to
> be more future proof I suspect VSTO is the way to go. If you are thinking of
> major projects now, VBA will be around and supported for long enough to
> satisfy the lifecycle of any application built with it.
>
> Just my £0.02
Leviatano
"Charles Maxson" wrote:
> I agree with what's been said on this thread. I think the great benefit is
> MSFT is keeping one current to Office (VBA) thru each release while building
> on the other one (VSTO), which gives developers a choice. Both of these have
> their merits and of course weaknesses, so it can often be an application by
> application decision on which to use when. If VBA (VB6) does it for you,
> stay there. Like Nick said, it is so tightly integrated its hard to ignore
> how well it works.
>
> If you can take advantage of the innovation in VSTO 2005 and the initial
> deployment is not a barrier, its worth a consideration. You can do a lot
> more with it than VBA but the bar is a bit higher for entry.
>
> ..... either way, you can get alot down by automating Office and you have