Obsolete API list for the .NET Framework 2.0

I have heard from several customers who have asked me what the differences are between the .NET Framework 1.1 to the .NET Framework 2.0 and whether or not they should migrate their existing .NET applications from 1.1 to 2.0.  This question does not have one simple answer, but one of the big factors in this type of analysis is whether or not a given application that was designed to run on the .NET Framework 1.0 or 1.1 will continue to function on the .NET Framework 2.0.  To help answer this question, Microsoft has published a list of APIs that have been marked as obsolete starting with the .NET Framework 2.0.  You can check out this MSDN site to take a look at the full list of .NET Framework APIs that have been flagged as obsolete between 1.1 and 2.0.

In a future blog post, I will look at some other facets of this question, including how publisher policy plays a role in deciding what version of the .NET Framework an application should target.


Skip to main content