Geek asks and answers

Excel (Office) and C #

At the moment, I have to support an Excel application consisting of many VBA modules . For me, this refers to the old system, and VBA looks like the language of recent days. Does it make sense to think about migrating to C # and the Office- based .NET application ? What are the pros and cons for such a migration, respectively, for automating Office with .NET in general? Or is VBA still the best way to develop Office applications and Office-automation? By the way, I am an experienced .NET developer.

+3
source share
2 answers

This is just an opinion, but I would advise you to stick with VBA for your standard development using Excel. Using .NET is definitely the next step, but it greatly simplifies Excel development.

Using .NET has many advantages, mainly regarding strong typing, but VBA has huge advantages over .NET when it comes to deployment. VBA is also a simpler language to start with, especially for working with Excel, which has many members that do not have typical return values.

, VBA , VB.NET # , Excel. , .NET , VBA, :)

!!!

+4

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

+3

More articles:


All Articles