Geek Answers Handbook

What works best with the user: VSTO or VBA macros?

I need to deploy an Excel file with minimal overhead and best ease of use.

Can anyone who survived tell me what provides the best user experience: Visual Studio Tools for Office (VSTO) or Visual Basic for Applications (VBA) macros?

The goal is to make excel act as an application interface that will be distributed to users. Both VSTO or VBA solutions will need to execute an HTTP request (possibly using MSXML6 or similar).

What are the differences that a user will see when using VBA or Excel? Signing a code or other actions will reduce any friction (or trust issue) they might encounter?

+5
source share
4 answers

Look first at VBA. The compelling argument for VBA is that once your VBA is written, you just need to provide the book to your user, and it just works. In addition, VBA loads faster than the VSTO add-in, for example.

On the other hand, updating a code can be a nightmare. How do you know that the user was messing with your VBA? What to do if there are several copies of the worksheet - are all relevant and you can reliably check the version?

VSTO , .NET . WPF, , -... . , , Excel,.NET- (, ). : ClickOnce , . , : , , , , , .

, VSTO Excel, VBA, , . , VSTO ( .NET, VSTO), , - , -.

, VBA VSTO . VBA Office, VSTO Visual Studio Visual Studio (Express). VBA - (record-macro FTW!), Visual Studio, . VB.NET # , , .

Jon49, , ExcelDNA, .NET Excel . .NET VSTO, "", VSTO.

, !

+13

VSTO - . XL-DNA, , .NET.

.NET, , , VBA, . - Express, .

, XL-DNA ( VB 2010 Express) VBA.

+4

VBA VSTO

0

VBA, .

?

  • VSTO
  • VBA .
  • VBA , !
  • VBA
-1
source

More articles:


All Articles