Geek Answers Handbook

Microsoft Visual Studio Tools for Office. Is it worth using?

Deploying VSTO code VSTO very cumbersome.

My use case I have to provide a certain structure of the content in the word. Am I better off doing all this in VBA?

+6
vsto officedev
source share
3 answers

It really depends on what makes sense for your project. If this is only for specific files and multiple users, I would recommend VBA.

If it is more complex and should work on all files for all users, I think that the VSTO plugin would be what you need. It really depends on your situation and the difficulty you are trying to provide.

+4
source share

Before VSTO 3.0, I would agree with Ryan Lansio, but was no longer. These days I have become so productive at VSTO that I do even small work at VSTO. This saved my ass on several occasions, as the add-on became very popular in the company, and all I had to do was add the path to the Click-once package :-)

+2
source share

Keep in mind that these are not only the limitations of VBA as a language, but also the lack of industrial strength tools such as unit test frameworks and source controls that can be frustrating. Because of this, you can trade the speed of development with long-term disappointment if you stick to VBA.

You could do both by writing VBA code to directly support your interface, and the rest in .NET.

0
source share

More articles:


All Articles