A .Net 2.0 Migration Strategy?

An anonymous reader asks: "I work for a large organization where we use .Net 1.1 as our sole development language. We have many frameworks, applications and web sites that are developed in .Net 1.1, and these developments are by no means trivial since 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?"

Comments

Re:I know this is trollish, but switch to Java

[GigsVT]

You'll just instead have to deal with silly Sun upgrades when they break things every few releases. I've never seen a Java app that didn't say "use this particular version of the JVM or all hell will break loose".