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:MS lifecycle and support

[Nazadus]

Would you like some cheese and crackers with that whine?

You don't _have_ to migrate. No gun is put to your head. It's not like they are going to make all computers uninstall 1.0 for 2.0. It's backwards compatible. That means, program in 2002 and .NET X.0 will work. It just means you don't get the nice new shiny features. If you want those AND the IDE, then they deserve their money. They have earned it.

Now, had you said "I want to program in WM5!" then you might have a partially valid argument. But you'r still ignorant as fuck.

Are you seriously wanting them to write features for FREE?!?

And even cooler -- if you are in college or school, get the Acedemic version of MS VS 2005 for $50 (like I did) from ccvsoftware.com.

Stop being a Linux fan boy and learn to make informed decisions.
You wouldn't last two seconds on the OpenBSD-Misc mailing list.