NET is not a language to use for new projects. To make it clear and without any spin - VB. NET Webforms, Workflow and WCF to name just a few defunct MS technologies that. NET, but it clearly isn't going anywhere new and that goes for classic ASP. It is what it is, but it will never be anything more. Due to differences in the platform, there will be some differences between Visual Basic on. NET Core that require language changes may not be supported in Visual Basic. This supports language stability and maintains compatibility between the. "Going forward, we do not plan to evolve Visual Basic as a language. Yes, sounds good too, but when language developers start to speak of stability you have to start to wonder where their ambitions have gone and the answer is: The significant number of programmers using Visual Basic demonstrates that its stability and descriptive style is valued. One of the major benefits of using Visual Basic is that the language has been stable for a very long time. Great, that's a big chuck of what most would want. This strategy described in this 2018 post has been replaced with the one in this post.Īnd the replacement post is a masterpiece of making bad news seem like good. But promises can be broken and now the blog post starts: Update: March 12, 2020 NET land after this - and everything looked good for the future. Visual Basic 16.1 and 16.2 will improve C# interop and add new features.Visual Basic 16.0 will ship at the same time C# 8.0 ships.The familiar Visual Basic Runtime is not yet part of.Visual Basic.NET compiles and runs on.NET programmers were nervous and then in 2018 a blog post by Kathleen Dollard said: NET was noticeable by the fact that few talked about it. NET can regain its importance after the transition.ĭuring all of this C# became the focus of language development efforts and VB.
NET system and hence much wasted time and confusion. NET Core is a good one, but it forces a complete reboot of the whole. NET Framework was, and is, being replaced by. NET was open sourced and chaos decended as. NET and go with UWP, aka Wint RT, aka Metro. Everything was fine - VB.NET kept reasonable pace with the development of C# and then things started to go wrong when MS decided to de-emphasize C# and. Its sole reason for existence is to provide continutity for the original Visual Basic. VB.NET is quite a nice language, but nothing special in the universe of languages. VBA is essentially VB6 with an application object model and this, despite lots of efforts and promises (threats?) to replace it, is still going strong and looks like hanging around a while longer. There are many programmers today who mourn the loss of VB6 and would like Microsoft to give it to the community by way of open sourcing it - which seems unlikely. The history is that Microsoft killed VB6 and attempted to replace it with an all-new. Visual Basic 6 and Visual Basic for Applications, VBA, are not Visual Basic. NET sort of followed on as an attempt to make VB 6 programmers think that they had somewhere to go. NET and C# were trailblazers and Visual Basic. Once Microsoft was a dynamic innovator in the language space. In its latest announcement Microsoft puts a positive spin on the confirmation that it no longer has a future.
#Microsoft visual basic for applications core bentley windows#
Visual Basic is arguably the language that made Windows accessible to the rest of us.
0 kommentar(er)
