VB.NET future roadmap - who owns it and where is it? I can't find a reference to it anywhere.
-
Follow
Oops, something didn't work.
Sign In to be begin to follow this thread
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.Getting "follow" information
Start following this thread
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.Removing your "follow"
Setting up your "follow"
Did you know you can
sign up for email notifications?
-
davewill
here birdie birdie, get in my belly!
-
felix9
the cat that walked by itself
usually they will talk about this in PDC, they revealed the async and iterators stuff at PDC10, maybe more will come in the next conference.
you can keep an eye on the vbteam blog and Lucian Wischik's blog, and Channel9 of course.
-
vesuvius
Count Orlock
@davewill:Anders Heijsberg now owns VB on top of C#, and both languages will be co-evolved, so what is in C# will be in VB and Vica-Versa
-
W3bbo
Work hard; increase production; prevent accidents, and be happy.
3 hours ago, vesuvius wrote
@davewill:Anders Heijsberg now owns VB on top of C#, and both languages will be co-evolved, so what is in C# will be in VB and Vica-Versa
If there's feature parity, what's the point of maintaining two different syntaxes?
(Not that I want XML literals in C#, of course)
-
felix9
the cat that walked by itself
syntax matters, to coders, its about tastes, culture, even religions
and the 'feature parity' thing is for major core features, surely you cant get every little syntax details interchangable, they are just different.
-
As felix says, the point of maintaining two different syntaxes is maintaining two different syntaxes.
-
davewill
here birdie birdie, get in my belly!
@vesuvius: Curious. Did Anders Heijsberb's ownership of VB start just after VS2005/.NET 2.0?
@felix9: Thanks. I had expected it to be on the Visual Basic Developers center of MSDN. Same for all the other centers on MSDN.
@W3bbo: VB RULES! okay that was 100% biased opinion. But to your point, the "end" constructs in VB are what always keeps me there over the ambiguous "}" in C#. The other thing that keeps me in VB primarily is that VB.NET was the tip of the spear in the earlier .NET years. That hasn't been the case in the most recent years. Thus my desire to think longer term and understand the road map and further make a best guess where things will be 5 years from now. [back of hand up to forehead, gazing into the air]
-
@davewill: I think it started around post VS 2008, Luca Bolognese has a classic C9 video on the co-evolution of VB & C# - http://channel9.msdn.com/blogs/charles/luca-bolognese-c-and-vbnet-co-evolution-the-twain-shall-meet
I'll give my .02 since I was the C# Product Manager and then the Lead Product Manager for Visual Studio Express Editions.
VB and C# (and C++ and J# ) were separate and at times competing teams. That meant that language, compiler, and IDE features were for the most part developed independently (the implementation of IntelliSense was a different code base depending on if you were in VB or C#). The original thinking was that VB and C# customers were different as personified by personas, Mort for VB, Elvis for C#, (and Einstein for C++). Each team had customer councils that would attend an SDR (software design review) to give feedback on the importance of language features. The issue was that this small base of customers wasn't always representative of the full customer base. A prime example was when we first discussed VS 2005 at PDC 2003, there was a lot of negative feedback on both teams that they wanted features the other team had since VB was implemented edit-and-continue and C# was added refactoring features (rename, extract method, etc). Additionally, VB developers wanted VB to have parity with VB language constructs, if C# gets generics, LINQ, etc, VB should get it as well. The VB and C# teams were later combined to be the languages team, although C++ still remains it's own separate entity.
Nowadays, it is primarily a syntax choice and most language/IDE features will work in both VB & C# with a few exceptions (ex: VB's XML literals or My).
-
davewill
here birdie birdie, get in my belly!
@Dan: Thanks Dan. Your information is good to get first hand. Prior to the last couple of years there was a concerted effort to demo and speak in regards to both C# and VB listeners. The last couple of years it seems to be C# only (to be fair 90% is a more accurate perception). Which isn't that bad when talking about existing language features. But when talking about new features or concepts it handicaps the VB listener who is trying to "imagine" the translation of the new content in real time. (if a channel 9 video could be run through a C#->VB converter now that would be something)
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.