The C# team posts answers to common questions and describes new language features
As you can see in the VS2013 Preview, we have not added new language features to C# and Visual Basic 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.
The most important is that we just shipped new versions of these two languages less than a year ago, with support for asynchrony being a major new and impactful language feature in both. Developers are still learning how to integrate and benefit from the asynchrony shift in languages and APIs. We are very excited about the quicker pace of release for VS, but we believe from experience that language versions need a little more time to settle in. Our current thinking therefore is that C# and Visual Basic should stay closer to the pace they have been on for the past decade. It’s a balance between providing stability and new value, and we feel like we already have that balance about right.
There is a more tactical reason for us as well, which is that we are nearly done reimplementing the compilers and language services for C# and Visual Basic from the ground up. You may have heard of this effort as the Roslyn project, and there will be many end user benefits to this work when it ships. From our internal perspective on the language team, the new infrastructure makes it vastly easier to implement and test new language features with confidence, quality and great tooling. While the old compiler infrastructure is rock solid and supports VS 2013 beautifully, any effort we spend implementing new language features on it takes away from investing in the tooling, language features and compiler APIs that will power the future.
We are actively working on the next versions of C# and Visual Basic. The language design team is in full gear, led by Anders Hejlsberg as usual, and we are considering lots of new language features, big and small. We are looking very much forward to sharing more details about this work as the ideas mature, and to ultimately ship these new language features in a future version of Visual Studio.
In the meantime, do enjoy VS 2013, and not least the improved async debugging!
About the Author
Mads Torgersen is the program manager for the C# language design and specification, and is also on the VB and TypeScript language design teams.
Makes sense. And I must stress again that the lang features and team should not work on the same release cycle as the tools themselves :)
Does that mean you will devote more time to fixing the GUI and bringing back setup and deployment projects?
Seems reasonable. Can't wait for Roslyn.
I'm surprised you guys aren't considering a more open, rapid-release cycle like the one you've implemented with TypeScript. IMO, the rapid-release and relatively tight-feedback loop between developers and community has been very successful. It's also nice to get features sooner rather than waiting 2+ years. I think it's something to be considered, even if it means the forced feature parity between C# and VB needs to be dropped.
Mads, you should consider reviving your blog!
Thanks for the great comments!
@ThomasX (and others interested): See my responses over at the VB team blog:
i totally agree with the idea that adding features to the language should take into consideration the ability of developers to learn them. and that speed might have increased somewhat in the last years but it is maybe still the same as the one we had when learing programming was reading the Kerningham & Richy C reference.
EXTENSION PROPERTIES FIX THIS, THEY'RE ONLY STILL JUST METHODS.
How about dropping VB and just focusing on C#! You can get rid of all VB tooling and slim down everything.
I too concur on the approach.
Appreciate your rapid release cadence for VS2012
That's good, because we're also still learning WCF (dead, replaced by Web API), WF (completely rewritten), and WPF (dead), all released in 2006.
I think C# is very powerful already. Because there are so many new features being introduced across .NET, including MVC 5 and other changes, I don't think more language-specific features are needed at this time. Slowing down the rate of change seems to be a wise choice.
visit dz link its useful
@more_wagons I don't understand this point of view. If you don't want to use new language features, don't use new language features. There are still companies coding with C# 3.
Thanks for clarify then issue but I am Always Asking why visual studio are not much Intelligence as Eclipse IDE ( Especially in Java) that can give you the direct solution for error that can programmer do it by him self let me Explain that
When we need to write the code for connecting UI with database we need to write the following code
SqlConnection con = new SqlConnection("");
but if I write it without Import the library (using System.data.SQlClient) will show me error
In eclipse this easily resolves by just click (ctr + shift+ o)
and Import the appropriate library
I hope understand what I am written about this will help the beginner programmer to know their mistakes easily