Breaking changes in .NET 4.0

Posted by Andrei Taptunov on Stack Overflow See other posts from Stack Overflow or by Andrei Taptunov
Published on 2010-03-30T19:37:45Z Indexed on 2010/03/30 19:43 UTC
Read the original article Hit count: 538

Filed under:
|

There is a lot of information about new features and classes in new 4.0 however there are also changes that may affect esixting applications, for example

  1. Timespan now implements IFormattable and old string.Format() with invalid options will throw exception instead of calling simple ToString(). However, CLR team provides a nice feature to enable behaviour from previous version with configuration setting - TimeSpan_LegacyFormatMode .

    CLR Inside Out

  2. Access to events inside the class where they are declared using += or -= will lead to call add/remove generated accessors that return void. Some code wan't even compile in 4.0.

    Chris Burrows Blog

  3. CAS is deprecated and to enable it one still need to use special setting in configuration - NetFx40_LegacySecurityPolicy

So I wonder what are other changes and is it possible to find at least preliminary list of changes that will or may break existing functionality with release of .NET 4.0 ?

© Stack Overflow or respective owner

Related posts about .net-4.0

Related posts about breaking-changes