tags:

views:

217

answers:

10

I just saw an interview with Luca Bolognese from the MS language team, and he mentioned that Anders Hejlsberg thinks developers should focus more on the BCL (base class library, framework) instead of lanugage features (C#, VB.NET).

Which class or interface in the current .net 3.5 framework should every developer know?

+3  A: 

This isn't a class, but if you're talking about 3.5 framework essentials then IQueryable is important to know.

Joseph
+1: I change my question to classes and interfaces
Peter Gfader
+2  A: 

System.String?

mackenir
+1: but I am not looking for the base types :-)
Peter Gfader
+2  A: 

The classes in System.Reflection and System.Diagnostics are quite powerful pieces of the framework that nobody seems to know.

jfar
I am looking more for specific classes
Peter Gfader
+3  A: 

If you're talking about .NET 3.5 specific classes, The LINQ extension methods in the static Enumerable class are (IMHO) the most important.

Philippe Leybaert
The funny thing with that is that the class Enumerable itself isn't really important, since many developers won't even know they're using it :D
OregonGhost
+4  A: 

Depending on WHAT you want to develop. I think most of us only (and only needs to) know parts of the whole framework.

xandy
+1. Yeah its tooo huge
Peter Gfader
+7  A: 

System.IO.Path. Really.

OregonGhost
debatable - System.Web is more important to me
annakata
System.Web is known to anyone who wants to do Web with .NET and not knowing it won't harm you. But System.IO.Path is typically unknown to many people, so they write their own path string handling routines, which usually results in broken software. Therefore I consider System.IO.Path an important class for every developer, in contrast to System.Web classes. And the author asked for specific classes, not huge namespaces.
OregonGhost
+5  A: 

Not 3.5 specific, but I would suggest two classes that gives for free what many writes code to solve: System.IO.Path (OregonGhost beat me by a few seconds on that one...) and System.IO.File. One underused gem in here is the method Path.Combine.

And also EventHandler<T>, instead of defining your own event delegates.

Fredrik Mörk
+1 for EventHandler<T>.
OregonGhost
+2  A: 

System.Object... all your classes inherited from it.

Adrian Godong
+1. HAHA ... Not what I was looking for, but you are so right!
Peter Gfader
+9  A: 

IDisposable and most of System.Collections.Generic spring to mind...

annakata
A: 

System.Int32

JaredPar