3 ms·
> Also remember that VB.NET, contrary to F#, enjoys equal footing with C# across all .NET deployment scenarios and Visual Studio graphical tooling. enjoyed. Mi
by cm2187 7y ago
> Also remember that VB.NET, contrary to F#, enjoys equal footing with C# across all .NET deployment scenarios and Visual Studio graphical tooling.
enjoyed. Microsoft pretty much annonced it was a legacy technology and that they will not maintain parity going forward. Which is the only reason I switched to C#.
- pjmlp 7y agoEnjoys. Try to do in F# many of the workflows VB.NET is capable of.
- jasode 7y agogp (cm2187) used past tense "enjoyed" for VB.Net because Microsoft officially stated back in 2017 that the newer platforms will be lead with C#: Excerpt from https://devblogs.microsoft.com/vbteam/digging-deeper-into-the-visual-basic-language-strategy/ https://devblogs.microsoft.com/vbteam/digging-deeper-into-th... : "But with regard to the cloud and mobile, development beyond Visual Studio on Windows and for non-Windows platforms, and bleeding edge technologies we are leading with C#." Microsoft made it very clear that VB.Net will not have equal footing with C# across all .NET deployment scenarios. The VB.Net being deliberately left behind for some future scenarios is a separate issue from your comparison with F#.
- pjmlp 7y agoJust like VB did not had and equal footing with C (VBX) and C++ (OCX), yet it did not bothered many non programmers to pick it up. This is the audience that Microsoft cares about. The kind of employees that outgrows their Office VBA macros, did not had any kind of CS background, and just wants to do some applications without having to create a custom IT order procurement for it, writing some code and dragging stuff out of the toolbox.