VSTO 2.0 vs Excel VBA

[Ben]

Hi There


I have started using VSTO, here are my list of pros and cons for VSTO,
what do you think?

Pros

(1) Developing a more future-proof solution, as MS is phasing out VBA
in favour of .NET

(2) All the advantages of .NET over VBA:
- Productive IDE that will improve over time (VBA IDE will not be
improved by MS)
- Better windows forms, with all .NET controls available
- Easier to consume Web Services
- Access to a fully featured programming language ... OO, Threads,
Generics, Delegates .. etc
- Access to all .NET BCL's
- Easier source control
- .NET Assembly is separated from xls, therefore can store assembly on
server and version control becomes easier

Cons

(1) No UDF's - This is a big deal for me, as I use UDF's in VBA
extensively

(2) No Macro Recorder - Although I have used Excel VBA for years and
don't "need" it, I find it an excellent starting point for most tasks.
If anything, it points me to the right place in the Excel object model.

(3) Licence costs - Need to buy VSTO separately to MS Office ! Another
$720 USD !! Significant cost for merchant banks that have several VBA
Warriors ... people who are not full time programmers, but use VBA to
improve their productivity

(4) Speed - I am finding VSTO to be significantly slower than VBA ...
presumably because VSTO uses Interop to communicate with Excel

(5) Deployment - I have not deployed a real VSTO app yet, but it
appears to be alot more complex than VBA

Cheers
Ben

 

[Jim Rech]

as MS is phasing out VBA in favour of .NET

Do you seriously think MS could or would drop VBA from Office? It will not
be enhanced much it's true, but to drop it would guarantee that no one would
upgrade. People/companies have _huge_ investments in it!

--
Jim
| Hi There
|
|
| I have started using VSTO, here are my list of pros and cons for VSTO,
| what do you think?
|
| Pros
|
| (1) Developing a more future-proof solution, as MS is phasing out VBA
| in favour of .NET
|
| (2) All the advantages of .NET over VBA:
| - Productive IDE that will improve over time (VBA IDE will not be
| improved by MS)
| - Better windows forms, with all .NET controls available
| - Easier to consume Web Services
| - Access to a fully featured programming language ... OO, Threads,
| Generics, Delegates .. etc
| - Access to all .NET BCL's
| - Easier source control
| - .NET Assembly is separated from xls, therefore can store assembly on
| server and version control becomes easier
|
| Cons
|
| (1) No UDF's - This is a big deal for me, as I use UDF's in VBA
| extensively
|
| (2) No Macro Recorder - Although I have used Excel VBA for years and
| don't "need" it, I find it an excellent starting point for most tasks.
| If anything, it points me to the right place in the Excel object model.
|
| (3) Licence costs - Need to buy VSTO separately to MS Office ! Another
| $720 USD !! Significant cost for merchant banks that have several VBA
| Warriors ... people who are not full time programmers, but use VBA to
| improve their productivity
|
| (4) Speed - I am finding VSTO to be significantly slower than VBA ...
| presumably because VSTO uses Interop to communicate with Excel
|
| (5) Deployment - I have not deployed a real VSTO app yet, but it
| appears to be alot more complex than VBA
|
| Cheers
| Ben