Community Convergence XLVIII


Welcome to the 48th Community Convergence. The C# team continues to work hard to get out the next version of C#, and to add improvements to the Visual Studio 2010 IDE. Working long, fruitful hours on these rainy Washington State January days and nights, the engineers on our team are doing a great job putting together a set of features that will improve both C#, and the experience C# developers have in the Visual Studio IDE. They are also working to lay the foundation for some big improvements which you will see only after the next version of C# ships.

To keep up with the team’s plans, you should:

  1. Continue to follow LINQ
  2. Learn about the Dynamic Features planned for Visual Studio 2010
  3. Learn about the Code Focused IDE features planned for Visual Studio 2010

Here are a few listings that will help you gain deeper insight into all of these important technology:

Videos

Sam Ng

Luca Bolognese

Eric Lippert

Kirill Osenkov

Soma

Matt Warren

 

 

kick it on DotNetKicks.com

Comments (4)

  1. You’ve been kicked (a good thing) – Trackback from DotNetKicks.com

  2. anthonyb says:

    "They are also working to lay the foundation for some big improvements which you will see only after the next version of C# ships."

    Hmmmm…like what ?! And you mean that we will see its in 4th version of the language or in the next one ??

    Thanks!

  3. I continue to be really disappointed with the way the C# team ignored the feedback it got and added dynamic features (which nobody asked for and could already be handled very easily in the existing framework) instead of more useful features like non-nullable arguments. It looks very much to me like a "hey, here’s a new toy, and we can implement it really easily, so let’s do it even if nobody cares about it".

    Yes, I’m sure 95% of C# programmers just can’t wait to write code using legacy COM components. Not.

  4. This is getting more and more important. Dynamics can cover some ground here but I think we really need them (IMHO). We need Synthetic Macros (Lisp macros not C++ ones) and it will for sure leverage a huge amount of coding burden. There are many good Statically Typed implementations of the concept out there (Nemerle, Boo and F# for example).

    If they are so terrifying we can use them in a enable/disable mode on our assemblies. We are doing this for Unsafe mode. Default mode can be disabled and I promise I will always enable it!