A group blog from members of the VB team
If you didn't get a change to make it to TechEd this year, fret not, we got it all on video for your viewing pleasure.
Join Principal Program Managers Dustin Campbell and Mads Torgersen as they give you the inside scoop on the future of VB and C#.
You'll learn about:
And better than just showing off all of these cool features you can get your hands on many of them today with today with the "Roslyn" End-User Preview. This preview includes the new code editing experience we're building for VB and C# as well as a smattering of new language features and a preview of the "Roslyn" APIs.
If you haven't had a chance to hear about the great things our team is working on for the future (or if you're so excited you just want to hear about them again) watch the video. And if you haven't already install the preview. Then ask us questions, here on the blog or on CodePlex and tell us what you like, what you love, what you hate, and what we're missing.
Also, over the next weeks we'll be diving into the features and the APIs shown in the video (and more) and how to use them. So keep checking back here for new content so you stay up-to-date with all the latest news about your favorite programming languages from your favorite team (and get the word out!).
P.S. If you haven't already please take a moment to fill out the Edit & Continue survey and tell us where we can be more awesome.
It is interesting how the actual title as used in the video (from 15 seconds in) is "The Future of C# and Visual Basic" but both this blog and the Channel9 page rename it to "The Future of Visual Basic and C#"...
I thought that was funny too. I used the title as it was printed on the TechEd page. And the description uses the VB/C# order again. The truth is that there is no particular order prescribed when talking about the languages together and different artifacts created by different people may appear with either order. I don't know if Mads or Dustin filled out the paperwork when registering the talk or who did the slides (which certainly were made after the title was registered) but I know Mads will sometimes mix it up intentionally just in case anyone is watching (like yourself) or depending on where he's posting, e.g.:
The MSDN library table of contents is also inconsistent msdn.microsoft.com/library
These funny little differences exist even internally on our email distribution lists (VB & C# team DL, C# & VB support).
But another interesting thing to note about all this randomness (aside from the human factor) is that the managed languages team consist of individuals who work or have worked more closely with one language or another in the past before we all unified and more often than not name order reflects where the person came from. For example, while I eventually came to be the program manager for both the VB and C# compilers I started out as the VB compiler PM for VS 2010. My colleague Alex was the compiler PM for C# in 2010. Dustin was the VB IDE PM but owns both now. Mads is the C# language PM and Lucian is the VB language PM.
At one point someone decided to just list languages in alphabetical order but then it became a matter of whether we call it C# (ahead of VB) or Visual C# (after VB). In some places we use Visual C# and in others we don't (there is actually a subtle distinction between the two). F# is even worse about it so it could appear at the end or in the middle of the list.
In short, we're all crazy :)
Do you write VB or C# in C++ or Use Old VB or C# to make New VB or C#
I am curious about it as
Although Roslyn source is mostly written in C# and some in C++
But VB Compiler is written in VB and C# Compiler in C#
It is very interesting but i suppose you write in C++ as vbc.exe of .Net Framework is Native!
We write the VB compiler, unit tests, and the various other layers of the VB workspaces and IDE in Visual Basic and vice versa for C#. If it's language-specific it's traditionally written in that language. Though the IDE team (whose source isn't available in open) does use VB.NET significantly in testing because they've invented their own XML-based DSL describing their tests and the VB XML literal feature really shines there.
Most of our shared components are written in C#. For example, the compiler uses a shared component for reading and writing metadata which I think takes advantage of unsafe code or something. I believe we also have some internal tools written in F#.
The old compilers were written in C++. We use C++ as a last resort. Currently I think we are still keeping the actual compiler drivers (vbc.exe and csc.exe) in C++ because they're really just entry points that send compilation requests to a compilation service we wrote which caches metadata between compiles to improve performance. Because they're such thin wrappers the time for loading the CLR and jitting the binary would be wasted so we wrote it (and its test) in native code. This was a sad moment in our history since it was the first C++ project introduced into the Roslyn solution (which at the time had some 80-100 projects all in managed code).
Strange they name it VB, everyone knows it is VB.Net.
Microsoft dropped VB6 for their own reasons.
They will drop VB.Net too.
VB6 is now Microsoft's most popular programming language (Tiobe index, May 2014)
The vote for an updated VB6 at the Microsoft Visual Studio User Voice site has now reached 7,000 votes:
Anew article from David Platt "VB6 and the Art of the Knuckleball"
David was also the author of "The Silent Majority: Why Visual Basic 6 Still Thrives"
It's our way or the highway Microsoft tells VB6 Developers
Microsoft have announced they will not add the same changes to the VB6 that they have already added to VBA. Microsoft's Paul Yuknewicz claimed those changes are "not possible" while "maintaining the essence" of VB6.
In refusing to support VB6 developers, Yuknewicz stated "VB6 was and still is without a doubt awesome. VB6 made developers incredibly productive building a breadth of applications and as a result we have a wealth of applications and passionate developers to this day in 2014. "
Yuknewicz naively assumes VB6 developers will "incrementally move forward to .NET" despite not having done so for the last 12 years.
Yuknewicz also claimed it would not be 'feasible' to open source VB6.
Yuknewicz does admit VB6 will be supported by Microsoft 'at least' through 2024.