Update on VBLang

I wanted to share a few things with you.

* I hope you heard the announcement that Visual Basic.NET will be in .NET Core 3!!!
* @jcouv just posted the [the Visual Basic language version history](https://github.com/dotnet/vblang/blob/master/Language-Version-History.md).
* We have started a conversation on guidelines for library authors on how to not exclude VB. Initial focus is the .NET Core framework libraries. (Example: provide overloads for `span` overloads).
* There is ongoing improvements in Visual Studio and Roslyn, such as a stream of Analyzers and Code Fixes, IOperation, and of course bug fixes.
* We have reviewed a handful of issues. This work will appear to be on/off, because of working on these other issues that we consider larger and because there are a lot of vacations in the summer. But we still plan to do this.

I am happy to be "the face of VB", but I don't want this to obscure how many people in Microsoft see Visual Basic.NET as an important part of .NET. The .NET Core 3 decision was made higher in the org by folks that think Visual Basic.NET **is** part of .NET. I am not fighting to make any of these things happen - I hear about many of them when the GitHub notifications come across my email.

I know we have a boatload of problems. I am not diminishing them by sharing that Visual Basic. NET **is** part of .NET.

We think .NET Core 3 is an important developer workload for Visual Basic.NET. VB is great at WinForms. Preliminary work has also made us realize the shortcomings of VB on .NET Core. There has been a bit of *mea culpa* on this. Clearly there is a chicken and the egg problem - VB isn't VB on .NET Core today (missing parts of the VB runtime and non-strict/explicit scenarios) so people aren't submitting bugs because it's so bad they aren't working in it (tell me I'm wrong), unless they are writing a VB dialect of C# development (tell me if any of you are doing that). The test apps I wrote didn't illustrate the size of the problem.

I wanted to post this today to restate that Microsoft is committed to Visual Basic.NET and to ask a few things:

* Stick with us. I know we've fallen short of your expectations, and I hope we'll be able to clarify the [Visual Basic.NET strategy](https://blogs.msdn.microsoft.com/dotnet/2017/02/01/the-net-language-strategy/) to clarify how we will prioritize developer workloads in the short/mid term soon.
* Can the community take on updating [the Visual Basic language version history](https://github.com/dotnet/vblang/blob/master/Language-Version-History.md)? We'll move this into the docs when it doesn't look like we did nothing prior to 15.0. I'd like to get this up faster than we are likely to get to it, because @jcouv and others are writing code.
* Is there someone that can explore and update us on the [Entity Framework code generation](https://github.com/bricelam/EFCore.VisualBasic). EF was designed to have plug-in generation (so that it could support VB), but the community needs to create the templates. I know that work started at the MVP Summit, but there has been no action in that repo for 3 months.

I believe in Visual Basic.NET as an experience, much more than a language. I want us to work toward an Open Source embracing community that reflects that. You are important to the future of VB.