3 ms·

I wish Microsoft would just make a CSA already, c# for apps. This would be a huge win on so many fronts that I am shocked they havent done it already. Increase

I wish Microsoft would just make a CSA already, c# for apps. This would be a huge win on so many fronts that I am shocked they havent done it already. Increase C# mindshare. Better Lang means a better ecosystem. It's a free win. It's also an ad for office. I started appreciating Outlook and Excel once I had vba filters and maps

flomo 7y ago
Very surprised after all these years (decades?) they have not done something like this. Basic has been a low priority at MS for a long time now.
- tonyedgecombe 7y ago
  It could have made for an interesting alternative to PowerShell as well.
  - animalnewbie 7y ago
    Not a PS1 expert by any means but you have to spend some time with it to appreciate the design decisions. It's a very "wholesomely" designed language. Try eg. The for each parallel construct which made me realize why the output in PS1 behaves how it does.
    - tonyedgecombe 7y ago
      That's always been the problem for me, I don't use it often enough to become fluent with it.
      - animalnewbie 7y ago
        You're missing out. As a full time Linux user (since a year), PowerShell is by far the best shell out there (once it starts after 5 secs)
        tonyedgecombe 7y ago
        I'm not going to start using it for the sake of it. Some tools I just dip in and out of when I need to. Build software is the same, I haven't modified my build scripts for a year.
oaiey 7y ago
Yeah, and considering that the .NET 5 runtime will run in WebAssembly this is quite interesting. Maybe they are porting VBA libs to .NET. Then C# and VB.NET can pick up. Or they do the real deal: Port VBA to .NET ... that however, would be a little bit difficult to explain with VB.NET in place as well ;)
markus_zhang 7y ago
It's just too much effort for nothing. People using VBA for automation pretty much live in the ecosystem of MS Office so it's not a big win for them. Plus MS has to spend huge sum of money to incorporate C# into Office. And we already have VSTO.

flomo 7y ago

Very surprised after all these years (decades?) they have not done something like this. Basic has been a low priority at MS for a long time now.

tonyedgecombe 7y ago
It could have made for an interesting alternative to PowerShell as well.
- animalnewbie 7y ago
  Not a PS1 expert by any means but you have to spend some time with it to appreciate the design decisions. It's a very "wholesomely" designed language. Try eg. The for each parallel construct which made me realize why the output in PS1 behaves how it does.
  - tonyedgecombe 7y ago
    That's always been the problem for me, I don't use it often enough to become fluent with it.
    - animalnewbie 7y ago
      You're missing out. As a full time Linux user (since a year), PowerShell is by far the best shell out there (once it starts after 5 secs)
      - tonyedgecombe 7y ago
        I'm not going to start using it for the sake of it. Some tools I just dip in and out of when I need to. Build software is the same, I haven't modified my build scripts for a year.

oaiey 7y ago

Yeah, and considering that the .NET 5 runtime will run in WebAssembly this is quite interesting. Maybe they are porting VBA libs to .NET. Then C# and VB.NET can pick up. Or they do the real deal: Port VBA to .NET ... that however, would be a little bit difficult to explain with VB.NET in place as well ;)

markus_zhang 7y ago

It's just too much effort for nothing. People using VBA for automation pretty much live in the ecosystem of MS Office so it's not a big win for them. Plus MS has to spend huge sum of money to incorporate C# into Office. And we already have VSTO.