Extend Support to VB.NET on Xamarin
MS can just use the existing VBA engine.
Expose the full VBA hierarchy to VB.NET, for development with VS Code.
Then MS won't have to invest in a Mac VBA IDE, and VBA developers will still get a great IDE.
another option, support Cocoa scripting
If you expose the VBA object hierarchy to Objective-C or Swift, then we can use Objective-C or Swift to create bindings to Excel, accessible to Xamarin.
Yet another option is to expose the Excel object hierarchy to Xcode/Swift on Mac OSX, so people can use NATIVE TOOLS.
My request is: TRADITIONAL EXCEL OBJECTS IN VB.NET.
NOT some new object hierarchy, NOT new object names, NOT new object properties and methods.
This option would also ease migration of existing VBA solutions.