.Net (VSTO) vs VBA

[Tammy]

I've been asked to estimate how long it will take to redo our
macros/templates (of which there are many) to .Net. The macros and
templates work well and I can see no good reason for this move. I've
asked for the business case behind this but have been told they "think
it will work better". Does anyone know the pros/cons of using .net
(VSTO) in place of Word's VBA? I know that there will be some
instances (maybe dlls?) where it would be better to use .net but
(besides dlls) I don't know of any. If anyone could provide more
information on this, that would be great!!
Thanks,
Tammy

 

[Howard Kaikow]

VSTO does NOT replace VBA.
The macros would still uses VBA.

If you want to use DLLs, using VB 6 is a lot easier than using VB .NET, not
to mention that VB 6 code is secure from prying eyes and VB .NET code isn't.