So, you’ve heard that VB (and C#) are open source now and you want to dive in and contribute. If you haven’t spent your life building compilers, you probably don’t know where to start. No worries, I’ll walk you through it.
[Update: You can get these cool T-Shirts @ the .NET Swag Store – get yours today!]
Mads and Dustin showed off their cool VB and C# team t-shirts at BUILD and tons of people liked them and asked where they could get one.
Thanks everybody for all the great feedback!
We’ve received hundreds of replies since last week with detailed information and concrete examples for us to review. We are closing the survey today and have started to process the tons of data you have provided.
The overwhelming majority of you have told us that Edit and Continue is important and you’d like us to make it even better.
UPDATE 2014-05-20: We’ve received enough responses and the survey is now closed. Thanks everyone!
Hey VB developers!
Do you get tired of seeing this box (I know I do)?
Tell us about it!
The Visual Studio team would like your anonymous feedback on improving Edit and Continue (E&C) when developing .NET applications.
UPDATE: QuickVB is now open source!
The Visual Basic team joins Dartmouth and developers worldwide whose lives have been touched by this amazing language in wishing Dartmouth BASIC (and indeed the whole BASIC family of languages) a very happy 50th birthday (and many more) today!
(For the next few posts, I’m going to introduce readers to the different feature teams in the Managed Languages org. Today, I’m starting this with a focus on the performance team.)
Back in 2000, I found myself assigned to be the performance lead of the Visual Basic team,
As you can see in the VS2013 Preview, we have not added new language features to Visual Basic and C# in the next version of Visual Studio. I’d like to share our thinking on this. There are essentially two main reasons why we chose not to evolve the languages this time around.