Base types, Collections, Diagnostics, IO, RegEx…
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.
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.
PingBack from http://microsoft-sharepoint.simplynetdev.com/whats-new-in-the-bcl-in-net-4-beta-1-justin-van-patten/
Visual Studio 2010 Beta 1 is available to try. Don't forget to download the Visual Studio 2010 and .NET
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.aspx
Thank you for submitting this cool story - Trackback from DotNetShoutout
.NET What's New in the BCL in .NET 4 Beta 1 How CLR maps SEH exceptions to managed exception types Announcing
Thank you for submitting this cool story - Trackback from progg.ru
Interesting Finds: May 24, 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...)
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 ?
>>> 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).
Agile Agility at Scale: Become as Agile as You Can Be: Scott Ambler talks about his new ebook; The goal of the Agility at Scale: Become as Agile as You Can Be ebook is to get people thinking outside of the box a bit when it comes to agile development
Where i can found a list of ALL changes in the .NET Framework 4.0 ?
It's really great that you folks got BigInteger in there. I look forward to seeing the System.Numerics namespace evolve.
This week on Channel 9, Brian and Dan discuss the top developer news including: - Bing - Microsoft's