Microsoft .NET Framework: CLR Futures

Play Microsoft .NET Framework: CLR Futures
Sign in to queue


Learn about the new features in the next major version of the Common Language Runtime (CLR) from the people building it. Hear about support for in-process side-by-side CLR version support. Get a look at development improvements including code contracts and tools, mini dump debugging in Visual Studio, and enhanced base class libraries including BigInteger, tuples, and trees. Learn how improvements to the GC allow for greater scalability for multiple processors and much more!
  • Joshua Goodman
    Joshua Goodman is currently the Group Program Manager for the Common Language Runtime team -- the team that builds the garbage collector, JIT (just-in-time-compiler), security model, hosting model, and base class libraries for .NET. Prior to that, he was Technical Assistant to Bill Gates, and before that he spent 8 years Microsoft Research, where he ran a small team. Many many years ago he was a developer at a speech recognition company.
  • Ian Carmichael



Download this episode

The Discussion

  • User profile image

    If I'm reading this right, finally having a way to generate useful minidumps for managed code will be a welcome addition.

  • User profile image
    I really like to hear some good news about improvements of JITed code quality, memory footprint. The reason I care about this is because one of my BubbleSort(Just swapping data between array elements) tests shows that .NET 3.5 sp1 is about 40% slower than its counterpart written in Java (JDK1.6 update10 with server GC enabled.)

    I am sure there are a lot of areas .NET did superior job, but why this big gap here?
  • User profile image
    Are code comments derived from or any way related to spec #? Will there be language support or only the class/object level?
  • User profile image
    The Design-by-Contract (CodeContract) is of course very Eiffelike, even the old-value semantics is there. The syntax is quite bloated in comparison [as leriksen71 says], but having the semantics at all is a first step. Also, tail recursion optimization is a welcome improvement.

Add Your 2 Cents