G
Guest
We're trying to decide whether to migrate a large .NET 1.1 (ELB 1.1) app to
..NET 2.0 or 3.0 (with ELB 3.1, probably)... within the next two months.
I've seen discussions that hint that the (long overdue) SP1 for .NET 2.0
will ship around the time that Orcas ships (early '08?). We could probably
tolerate that if we migrate the app to 2.0 now.
On the other hand, if we migrate to 3.0 now, when will SP1 for .NET 3.0
ship? Since 3.0 is purportedly an extension to 2.0, and isn't supposed to
have changed the "core" of 2.0, would we be able to apply 2.0 SP1 to 3.0?
But if the 2.0 SP1 doesn't also apply to 3.0, and the 3.0 SP1 will be even
later (1.5+ years, as the 2.0 SP has proven to be), then there's no way we
could consider migrating to 3.0 now...
DT
..NET 2.0 or 3.0 (with ELB 3.1, probably)... within the next two months.
I've seen discussions that hint that the (long overdue) SP1 for .NET 2.0
will ship around the time that Orcas ships (early '08?). We could probably
tolerate that if we migrate the app to 2.0 now.
On the other hand, if we migrate to 3.0 now, when will SP1 for .NET 3.0
ship? Since 3.0 is purportedly an extension to 2.0, and isn't supposed to
have changed the "core" of 2.0, would we be able to apply 2.0 SP1 to 3.0?
But if the 2.0 SP1 doesn't also apply to 3.0, and the 3.0 SP1 will be even
later (1.5+ years, as the 2.0 SP has proven to be), then there's no way we
could consider migrating to 3.0 now...
DT