What's New in the BCL in .NET 4 Beta 1 [Justin Van Patten]
Visual Studio 2010 and .NET Framework 4 Beta 1 are available for download. .NET 4 Beta 1 contains new functionality and improvements throughout the framework. In this post I’ll discuss the changes specific to the BCL.
Many of the features listed below were previously announced when we released the .NET Framework 4 CTP back in November of last year. I’ve included these features again below for completeness. New functionality in Beta 1 that wasn’t present in the CTP is denoted as such.
Code Contracts
System.Diagnostics.Contracts provides a language-agnostic way to express coding assumptions in .NET programs. The contracts take the form of pre-conditions, post-conditions, and object invariants. Contracts act as checked documentation of your external and internal APIs. The contracts are used to improve testing via runtime checking, enable static contract verification, and could be used in documentation generation. We partnered with Microsoft Research to deliver this feature in .NET 4. More information and links to the tools are available on the Code Contracts DevLabs site.
(new in Beta 1) The latest release of the tools works with Visual Studio 2010 Beta 1.Parallel Extensions
The Parallel Computing Platform team worked with us to add the Task Parallel Library (TPL), Coordination Data Structures, and Parallel LINQ (PLINQ) to the BCL in .NET 4. This includes an improved ThreadPool scheduling algorithm for tasks, Task and Task<T>, the static Parallel class, concurrent collections in System.Collections.Concurrent, and other coordination data structures such as Lazy<T>, CountdownEvent, Barrier, SemaphoreSlim, SpinLock, SpinWait, and ManualResetEventSlim. More information is available over at the PFX team’s blog.BigInteger
System.Numerics.BigInteger is an arbitrary-precision integer data type. BigInteger supports all the standard integer operations, including bit manipulation. It can be used from any .NET language, and some of the new .NET languages—such as F# and IronPython—have support built-in to the language. We partnered with the Microsoft Solver Foundation team to deliver this in .NET 4.Variance annotations (new in Beta 1)
C# and VB now support safe co- and contra-variance for generic interface and delegate types. Co-variance means that a generic of a type, e.g. an IEnumerable<String>, can be treated as a generic of any supertype, e.g. an IEnumerable<Object>. Contra-variance means that a generic of a type, e.g. an Action<Object>, can be treated as a generic of a subtype, e.g. an Action<String>. In C#, co-variance is annotated with the “out” keyword and contra-variance is annotated with the “in” keyword. VB has similar “In” and “Out” keywords. We’ve annotated several interfaces and delegates in the BCL for variance, including: IEnumerable<T>, IEnumerator<T>, IComparer<T>, IEqualityComparer<T>, IComparable<T>, the Action and Func delegates, Predicate<T>, Comparison<T>, EventHandler<TEventArgs>, and Converter<TInput, TOutput>.Tuples (new in Beta 1)
We’ve added common Tuple types in the BCL to facilitate language interoperability and to reduce duplication in the framework. A tuple is a simple generic data structure that holds an ordered set of items of heterogeneous types. Tuples are supported natively in languages such as F# and IronPython, but are also easy to use from any .NET language such as C# and VB.SortedSet<T> (new in Beta 1)
We’ve added a SortedSet<T> collection along with a new ISet<T> interface. SortedSet<T> uses a self-balancing tree which maintains data in sorted order for performance guarantees with insertion, deletion, and searches. Both the new SortedSet<T> and the existing HashSet<T> implement ISet<T>.File System Enumeration Improvements (new in Beta 1)
System.IO.Directory and System.IO.DirectoryInfo have new APIs for enumerating the file system that return IEnumerable<T>s instead of arrays. These new APIs are more efficient than the array-based APIs because they do not need to allocate a (potentially large) array and you can access the first results immediately instead of waiting for the entire array to be created and returned. We’ve also added new convenience APIs for efficiently reading, writing, and appending lines from/to a text file using IEnumerable<String>. These new APIs are useful in LINQ scenarios where you may want to quickly and efficiently query the contents of a text file and write out the results to a log file without allocating any arrays.MemoryMappedFiles
System.IO.MemoryMappedFiles exposes the memory mapping functionality provided by Windows as first-class managed APIs. Memory mapped files can be used to efficiently edit very large files and can also be used to create shared memory for inter-process communication. Along with this feature, we’re introducing System.IO.UnmanagedMemoryAccessor, a new class that enables random access to unmanaged memory similar to how UnmanagedMemoryStream enables sequential access to such memory.Registry Improvements (new in Beta 1)
We’ve added support to Microsoft.Win32.RegistryKey for accessing alternate registry views (32bit and 64bit views) on 64bit Windows. We’ve also added the ability to create volatile keys—keys that are stored in memory and are not persisted when the hive unloads (which typically happens on reboot). In addition, we’ve added new extensibility APIs that take and return a SafeRegistryHandle to make it easier to interoperate with Win32 registry APIs that do not have managed wrappers.Globalization data updated to Unicode 5.1 (new in Beta 1)
Culture data in .NET 4 has been updated, including updating the character information to Unicode 5.1. We have also added support for new cultures, including new neutral cultures.ResourceManager Improvements
The ResourceManager in System.Resources has been improved to respect the user’s preferred UI languages when looking for localized resources, instead of only using the CurrentUICulture’s parent chain. This means if the user has specified in Windows that she prefers French and Spanish, the ResourceManager will look for French and Spanish resources before falling back to the neutral resources. This change is present in Silverlight 2 as well as .NET 4.Compression Improvements
The compression algorithms in System.IO.Compression have been improved in .NET 4. DeflateStream and GZipStream no longer inflate already compressed data. This means that in many cases you’ll see better compression ratios when using these streams on .NET 4. We’ve also removed the 4 GB size limit, so you can now compress streams over 4 GB in length.
You can learn more about what’s new in the BCL in .NET Framework 4 on Channel9: Inside .NET 4: Meet the BCL Team.
We hope you enjoy the new functionality and improvements in Beta 1. Be sure to let us know if you run into any issues or if you have any further suggestions. And look out for even more improvements and refinements in the next preview release of .NET Framework 4.
Comments
Anonymous
May 22, 2009
PingBack from http://microsoft-sharepoint.simplynetdev.com/whats-new-in-the-bcl-in-net-4-beta-1-justin-van-patten/Anonymous
May 22, 2009
Visual Studio 2010 Beta 1 is available to try. Don't forget to download the Visual Studio 2010 and .NETAnonymous
May 23, 2009
Interesting stuff : http://blogs.msdn.com/bclteam/archive/2009/05/22/what-s-new-in-the-bcl-in-net-4-beta-1-justin-van-patten.aspxAnonymous
May 23, 2009
Thank you for submitting this cool story - Trackback from DotNetShoutoutAnonymous
May 23, 2009
.NET What's New in the BCL in .NET 4 Beta 1 How CLR maps SEH exceptions to managed exception types AnnouncingAnonymous
May 23, 2009
.NETWhat'sNewintheBCLin.NET4Beta1HowCLRmapsSEHexceptionstomanagedexception...Anonymous
May 23, 2009
Thank you for submitting this cool story - Trackback from progg.ruAnonymous
May 24, 2009
Interesting Finds: May 24, 2009Anonymous
May 26, 2009
Variance annotations: this is great! but why don't you add additional interfaces that enable covariance for more complete collections? e.g., IList<T> has T in input and output positions, so it cannot be covariant. however, IEnumerable<> is very limited, so whenever I need covariance, I'd have to cast to IEnumerable<T> and just enumerate that list. you could provide additional interfaces such as IReadonlyCollection<out T> or IReadonlyList<out T> that use T only in output positions, so we could get covariance AND the ability to clear list, access them by position, get a count and everything without doing a (slow) enumeration. Whether ICollection<T> would inherit from IReadonlyCollection<T> is a matter of compatibility (some reflection-based code may rely on the current inheritance hierarchy), but at least additional interfaces sure would not hurt. (As a side note I find it interesting that in all interfaces up to IList<T>, there are only two methods that are not covariant by nature: Add and Insert. E.g., ignoring the static type system for a moment, Remove(T obj) is perfectly covariant: trying to remove an object of the wrong type should have the exact same effect as trying to remove an object of the correct type that's just not in the collection. Only Add and Insert could get us into additional trouble at runtime. Obviously, that's nothing a static type system can easily account for, but a specialized ICovariantList<T> could easily provide object-Typed methods for those instances. But then again, it's probably the most straightforward way to just use the non-generic ICollection/IList interfaces for such stuff...)Anonymous
May 26, 2009
I noticed that the Tuple with the TRest parameter is enforcing that TRest is ITuple in runtime, instead of declaring the type parameter as TRest : ITuple. Is there any good reason behind that ? Omer Mor.Anonymous
May 26, 2009
>>> I noticed that the Tuple with the TRest parameter is enforcing that TRest is ITuple in runtime, instead of declaring the type parameter as TRest : ITuple. Is there any good reason behind that ? Well, there's no interface ITuple. And even if there was, nothing would restrict someone else from implementing it, either (it would have to be public to be used in a generic constraint).Anonymous
May 27, 2009
The comment has been removedAnonymous
May 27, 2009
Hi, Where i can found a list of ALL changes in the .NET Framework 4.0 ? Thanks!Anonymous
May 28, 2009
It's really great that you folks got BigInteger in there. I look forward to seeing the System.Numerics namespace evolve.Anonymous
May 29, 2009
This week on Channel 9, Brian and Dan discuss the top developer news including: - Bing - Microsoft'sAnonymous
May 29, 2009
Why is BigInteger is Numerics namespace? shouldn't it be where Int32 and the others are?Anonymous
June 02, 2009
The comment has been removedAnonymous
June 02, 2009
very informative blog post, thanks!Anonymous
June 06, 2009
Muchas son las novedades que tenemos en la BCL (Base Class Library) de .NET Framework 4.0…y para conocerlasAnonymous
June 11, 2009
ヒマだょ…誰かかまってぉ…会って遊んだりできる人募集!とりあえずメール下さい☆ uau-love@docomo.ne.jpAnonymous
June 13, 2009
カワイイ子ほど家出してみたくなるようです。家出掲示板でそのような子と出会ってみませんか?彼女たちは夕食をおごってあげるだけでお礼にHなご奉仕をしてくれちゃったりしますAnonymous
June 14, 2009
あなたは右脳派?もしくは左脳派?隠されたあなたの性格分析が3分で出来ちゃう診断サイトの決定版!合コンや話のネタにも使える右脳左脳チェッカーを試してみようAnonymous
June 16, 2009
The comment has been removedAnonymous
June 16, 2009
セレブ達は一般の人達とは接する機会もなく、その出会う唯一の場所が「逆援助倶楽部」です。 男性はお金、女性はSEXを要求する場合が多いようです。これは女性に圧倒的な財力があるから成り立つことの出来る関係ではないでしょうか?Anonymous
June 17, 2009
貴方のオ○ニーライフのお手伝い、救援部でHな見せたがり女性からエロ写メ、ムービーをゲットしよう!近所の女の子なら実際に合ってHな事ができちゃうかも!?夏に向けて開放的になっている女の子と遊んじゃおうAnonymous
June 18, 2009
На другом сайте это уже я читала.[url=komsomolsk-na.ru ] [/url].[url=http://9990086.ru ] [/url]Интересный сайт,[url=gorno-altajsk.ru ] [/url]спасибоAnonymous
June 20, 2009
家出中でネットカフェやマンガ喫茶にいる女の子たちは、お金が無くなり家出掲示板で今晩泊めてくれる男性を探しています。ご飯を食べさせてあげたり泊めてあげることで彼女たちはHなお礼をしてくれる事が多いようです