c# directly in Office
Office continues to use the dead language VBA for macros. Using the Roslyn project, it should be easier to allow C# to be written directly within Office. This would be a huge, huge improvement over having to write and maintain VBA macros.
VSTO and VSTA are a clunky solution at best, and deployment of Office apps using them is always an issue. Making Office natively support C# is the solution.
Hi Jack, thank you for the idea! Although we appreciate your time and effort to give us this feedback, this doesn’t align with the general strategic vision of our products.
I have coded in Java, C, Assembly languages for 8 bit to x86 to Arm, PHP, Python. Nothing makes me feel at home like VB. I dread coding in VB.net in UWP. As a work around I first code in VB.net in winforms, debug then port it to UWP. If VB was rightly promoted at the right time Python and many other languages would be still born. Windows CE would have eclipsed Android. I have created long serving products using VB6 as front end (with back end communicating with hardware and running DSP algorithms in assembly and C, serving the medical community) and I am always indebted to VB.
Yes, keep VBA programming in Office. No Office user or developer wants C# - it's too big, too complex and too slow.
JT Smith commented
VBA isn't an unsupported or unmaintained language. And it is far better than VSTO or VSTA. C# is just an overblown and over-complex solution for Office.
A better idea would be to add VB6 programming to Office.
So the "strategic vision" of the Office team is to continue shipping an unsupported, unmaintained language that has been dead for almost a decade as the de-facto method of automating Office? That sounds like a much better idea than leveraging Roslyn and C#.
This arrogant line of thinking from the Office division is why it continues to hemorrhage market share.