Preparing for V2.0 of the .NET Framework
I just noticed that in all the excitement of the BCL team’s blog day, I missed that Kit published a list of all the members of the .NET Framework that were obsoleted in V2.0. Notice that many of this were introduced and removed in V2.0, so the churn is much less than it looks. And, of course your apps keep working even if they are using these…
As Kit says, the best way to test your app out is to download the latest bits and try it… but it still might be interesting to look at the data in this format.
Here are a few from MSCorLib to give you an example:
| System.String |
| Split(Char[] separator,Boolean omitEmptyEntries) | Message: This method will be removed soon. Please use Split(char[], StringSplitOptions). |
| Split(Char[] separator,Int32 count,Boolean omitEmptyEntries) | Message: This method will be removed soon. Please use Split(char[], int, StringSplitOptions). |
| Split(String[] separator,Boolean omitEmptyEntries) | Message: This method will be removed soon. Please use Split(string[], StringSplitOptions). |
| Split(String[] separator,Int32 count,Boolean omitEmptyEntries) | Message: This method will be removed soon. Please use Split(string[], int, StringSplitOptions). |
| |
| System.Reflection.Assembly |
| PortableExecutableKinds | Message: Please use Assembly.ManifestModule.GetPEKind() instead - this will be removed before Whidbey ships. |
| ImageFileMachine | Message: Please use Assembly.ManifestModule.GetPEKind() instead - this will be removed before Whidbey ships. |
| MetadataToken | |
