Converting from VBA to VB .NET
-
- I have an application that is developed using VBA for automating excel spreadsheets to create and accounting system. Is it advisable to migrate the code to VB.NET going foward, e.g. for consideration of continuity will VBA continue to be as is, backward compatible or is vb.net going to be language of choice with applications?
-
- I have an application that is developed using VBA for automating excel spreadsheets to create and accounting system. Is it advisable to migrate the code to VB.NET going foward, e.g. for consideration of continuity will VBA continue to be as is, backward compatible or is vb.net going to be language of choice with applications?
Microsoft has announced no plans to replace VBA with VB.NET. So, for at least the next version of Office, VBA is still going to be what's built into it.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak -
- I have an application that is developed using VBA for automating excel spreadsheets to create and accounting system. Is it advisable to migrate the code to VB.NET going foward, e.g. for consideration of continuity will VBA continue to be as is, backward compatible or is vb.net going to be language of choice with applications?
VBA will continue to work. Corporations won't upgrade Excel if Microsoft killed VBA since so many macros have been written. Upgrading Visual Basic (not VBA for Excel) to VB .NET is a nuisance. If you had to port a significant amount of code, you also could consider C#. I personally prefer to use Excel C API as much as possible, and a minimal amount of VBA.