VSTO vs VBA - some new questions

Hi Gideon,

What do you want is possible to achieve with Visual Studio, and Visual Studio Tools for Office (VSTO).

I use to develop on VSTO, not in VBA, so I can advice you comparing both tools.

What I can tell you is about upsides an downsides of VSTO:

• Good. Full .NET support. That means a lot of already-developed libraries, means less required efforts, means money.
• Good. You can use Parallel Extensions to perform the number-crunching calculations (if they are parallelizable).
• Good. Fast development. Customizing a Ribbon is a trivial task.
• Bad. Deployment. The end-user machines will need to have VSTO Runtime, .NET and Office Interop Assemblies (unless you're targeting Office 2010).