Free LiveMeeting with the CLR Team on CLR 4 [Justin Van Patten]

Join the CLR team for a free interactive LiveMeeting session / conference call on What's New in CLR 4 on Friday, July 17, 2009.  We'll specifically be covering Garbage Collection, NGEN, and Performance.

Here are the details:

Date: Friday, July 17
Time: 10:00AM-11:00AM PST


Conf call:
Toll Free: 866-500-6738
Toll: 203-480-8000
Participant code: #198585

Comments (4)

  1. Andrei Rinea says:

    For those of us who won’t be able to attend it will we find it somewhere recorded? 🙁

  2. SealedSun says:

    I, too, would be very interested in a recording.

  3. BCL Team says:

    Andrei, SealedSun,

    Yes, we’ll try to get a recording posted on Channel9 within a few weeks of the LiveMeeting.  When its available we’ll blog about it.


    Justin Van Patten

  4. Ark-kun says:

    Sorry for the rant. I don’t think anyone would read this so I can just write my thoughts.

    1)BCL is becoming too redundant. There are many methods/classes here and there that do the same.

    Search for the word "collection" in reflector. See this enormous list?



    etc, etc. Many of these classes do not even implement ICollection or IEnumerable. Most of these classes have nearly identical implementation. Another issue is that you cannot just inherit from List or Dictionary and override some methods.

    Brus, Point, Vector, Matrics… When will this stop?



    //Do they at least have a common ancestor? No.








    //Do you think that there is at least single REAL matrix class? The answer is NO.

    2) When I see the System.Windows.Media.Media3D namespace I want to cry. The class system is good, but it’s tied (or better said nailed) to the implementation.

    3) The BCL is sealed too much. Is there any classes that let you send HTML forms over HTTP in "multipart/form-data" format? Yes, they exist. internal!

    4) BigInteger? internal! {fixed in .Net 4}

    5) LINQ-to-SQL is open and developers have created many LINQ providers. What about LINQ-to-XML? Can we create LINQ-to-HTML  for example and use the same syntax? Of course no. The classes are completely sealed. From architectural point of view there should be some generic Tree and Node classes with parts of LINQ-to-XML built on top of them. The XML document is just a tree with a collection of attributes as the node value type.

    6) {fixed in .Net 4}: Why did you make System.Linq.Expressions.ExpressionVisitor class non inheritable? Instead you published it’s code on MSDN and asked to copy&paste it into the program.

    7) Library names were meaningful and consistent. Then some "PresentationFramework.dll", "PresentationCore.dll", "WindowsBase.dll" and "System.Core.dll" started appearing. Are we going to see "NextLib.dll", "System.Cool.dll", "HelloWorld.dll" and "untitled.dll"?

    8) Excessive usage of non-generic types and collections. BTW, where is the ICloneable<T>?

Skip to main content