Support for obsolete methods

microsoft.public.dotnet.framework

10 Nov 2005 8:38 PM

n33470

We're in the planning phase for how to migrate our apps to the .NET 2.0
framework.   We have a bunch of common assemblies and two UI platforms
(Web and Windows).   Both of the UI platforms reference the common
assemblies. The Web apps will be migrated first, and a few months
later, the Windows apps will follow. The question revolves around the
best way to deal with the common assemblies.

The common code references a bunch of deprecated classes. For example,
the use of Configuration.ConfigurationSettings has been deprecated with
Configuration.ConfiguationManager.   Our code references other
deprecated classes, this is just one example of many.

We plan to compile the common code for each of the target environments
separately (one set built in VS2003, and the other in VS2005), but I'd
like to manage only one version of the common source code files.

After both platforms are migrated, then we'll refactor the common
source code to replace all the deprecated classes.

Can you think of any reason that this might not work, or be undesirable
in any way?

Thanks!

--steve