Much of what you can do with .NET, from a compositional perspective, is enabled by the vast functionality housed in .NET’s huge base class libraries (in fact, the BCL is what provides all the incredibly default(part of .NET framework) useful objects you use to paint your binary vision). Who’re some of the folks who think up and write BCL? Who tests BCL to ensure these libraries do what they claim to do and in a performant, reliable and predictable way? What’re some of the innovations in BCL that ships as part of Visual Studio 2010? Tune in and find out the who, what and why behind BCL 4.
- Long Paths in .NET, Part 1 of 3
- Long Paths in .NET, Part 2 of 3: Long Path Workarounds
- Long Paths in .NET, Part 3 of 3 Redux