.Net 2.0 Migration Strategy

  • Thread starter Thread starter garethdjames
  • Start date Start date
G

garethdjames

I work for a large organisation where we use .Net 1.1 as our sole
development language.

We have many frameworks and applications and web sites that are
developed in .Net 1.1

These developments are by no means trivial, they are the result of an
IT department of over 300 people and 2 years of development

It is my responsibility to develop a strategy to move to .Net 2.0, this
includes the existing applications, new developments, integration, QA,
live and development environments

Does any one have any experience in this (preferably at this scale) and
can any one recommend any reading material that would help.

Thanks

Gareth
 
I work for a large organisation where we use .Net 1.1 as our sole
development language.

We have many frameworks and applications and web sites that are
developed in .Net 1.1

These developments are by no means trivial, they are the result of an
IT department of over 300 people and 2 years of development

It is my responsibility to develop a strategy to move to .Net 2.0,
this includes the existing applications, new developments,
integration, QA, live and development environments

Does any one have any experience in this (preferably at this scale)
and can any one recommend any reading material that would help.
Click to expand...

I'd take it one project at a time, starting with assembly consuming
projects, thus projects which consume libraries you also use in other
projects, for example websites or desktop apps.

Start with a project that isn't that mission critical and use it as a
trial migration. Also do a website migration and see which roadblocks
you run into, for example 3rd party controls, the change from
webprojects in .net 1.x to directory based projects in .net 2.0. Use
these learning processes as guidelines for the rest of the projects.

Do the assemblies other projects depend on as the last projects, as
..NET 2.0 is capable of running .net 1.x compiled code just fine,
however the other way around is a bit cumbersome ;)

FB

--
 
Back
Top