5/15/2023 0 Comments V isual studio![]() ![]() We took the time to reconsider, adjust and recommit to our strategy. ![]() We are also committed to open source, backwards compatibility, and aggressive language evolution for C# and F#. NET team said " we do not plan to evolve Visual Basic as a language."ĭollard this week also said, "We remain committed to full support for all three languages. That's not too different from the company's remarks way back in 2020, when the. We will continue to invest in the experience in Visual Studio and interop with C#, especially in core VB scenarios such as Windows Forms and libraries." We do not plan to extend Visual Basic to new workloads. NET Runtime introduce new features that would require language support, VB will generally adopt a consumption-only approach and avoid new syntax. NET Runtime and libraries will automatically benefit VB. NET (such as the BCL) will support VB and many of the improvements to the. The corresponding and updated VB guidance says: "We will ensure Visual Basic remains a straightforward and approachable language with a stable design. ![]() In that post, Dollard said, "We remain committed to Visual Basic and continue to invest in maintaining C# interop and Visual Studio features for folks that love Visual Basic or want a stable language." There were changes for VB, though, as documented in the company's " Annotated Visual Basic language strategy," which was updated on the same day as Dollard's post (Feb. The gist of the update, as author Kathleen Dollard said several times in the update blog post and on social media, is that "You won't find big changes." Microsoft updated its programming languages strategy, confirming that Visual Basic will remain a going concern even though it's still relegated to second-rate status when compared to C# and F#.
0 Comments
Leave a Reply. |