Blog Post

.NET 4.5: BCL Team - Improvements and Evolution

Play .NET 4.5: BCL Team - Improvements and Evolution

The Discussion

  • User profile image

    Downloading this, but here is a related story. Smiley

    InfoQ: The Story of Read-Only Collection Interfaces in .NET

  • User profile image

    Great stuff.  Read only collections are important for optimizing and making thread safe code, so +1 for that. ReflectionContext sounds great ... reading up on it now.




  • User profile image

    Haha, the laughing in the background when charles mentioned the suggestion of rewriting wpf designer in native!

    Btw, the bcl team is allowed for iphones?!

  • User profile image

    @philjay: Maybe it was nervous laughter (just kidding) Smiley

    What do you mean by "allowed"? Microsoft employees are free to use whatever consumer device they prefer. You know, like consumers.... That said, most Microsoft employees are using Windows Phones these days (it's only been available for one year....). When we are able to get our hands on Nokia Windows Phones and other modern hardware-based mobile devices, I suspect iPhones will be quite hard to spot (or hear, as in this case...) around Microsoft. Dan just got the latest edition of the Focus - and I'm jealous. Front-facing camera, sleek, solid, bright display, fast.

    Mango is slick. I'm impressed and I generally don't get impressed by mobile phones or mobile phone operating systems...

  • User profile image

    Just started watching, but as you have someone from Portable Projects, any chance support for  ObservableCollection is going to be added?

  • User profile image

    Any chance at a SIMD API like mono provides? Seems like that (along with appropriate improvements on the xbox JIT) would lead to a tremendous performance boost for XNA applications, particularly when it comes to all the Vector4 and Matrix math operations involved in physics simulation.

  • User profile image

    Actually, you can have a List that is both covariant and contravariant by giving it two type parameters: List<out Read, in Write>. Then you use the right type for each method. For example Add(Write elem) and list.First has type Read. Now you can pass a List<string,string> to a method that reads objects from that list, and pass a List<object,object> to a method that writes strings to that list.

Add Your 2 Cents