MS and the upgrade frenzy
-
I just stumped on this in a newsgroup : "Frustrating finding the 1.0 framework @ microsoft.com for installation on my client's server." --> For those who wouldn't get it, the guy says it's now impossible to find the .NET framework 1.0, that was until April24 the only run-time available for .NET, and was working hand-in-hand with VS.NET 2002. By removing .NET 1.0 from the download sites, MS is aggressively ensuring we upgrade to VS.NET 2003. (VS.NET 2002 exclusively uses .NET 1.0, and MS made sure with VS.NET 2003 that VS.NET 2003 would purposedly only be able to use .NET 1.1). Looks like MS does not care about customers developing 1.0 .NET projects. What fucking policy is that ? As a result, for those who would start .NET 1.1 projects from now on, what ensures them that MS does not come next year with a breaking .NET 2.0 upgrade ? All this would seem may be a bit childish if the .NET upgrades were backward compatible. Unfortunately, that's not the point : .NET components are tightly coupled with very costly VS.NET products. "Funny how when Microsoft moves on to something new, they flat abandon everything they used to go bananas over just weeks prior. When VS.NET came out, all VB6 articles completely vanished. They suck like that. I don't like it. I still have to install my October, 2000 MSDN CDs to get full legacy documentation for VS6." --> Read and learn. MS is silently removing significant topics from MSDN. The topics are removed claimwise because they are discussing plumbing. But in practice, plumbing is the very heart of Windows programming, as a whole. Experienced programmers know that a lot standard Windows programming details, techniques, protocols, know-how cannot be found anymore in MSDN since 2001, when MS decided it was 100% focusing on .NET. Another example : on September 2002 MS silently removed all Windows 9X/NT/2000 DDKs (device driver kits) from their download site, ensuring that only the latest Windows XP DDK remained available. Just in case customers would have forgotten to upgrade to Windows XP before they finished their projects dealing with DDK. So my question is : let aside technologists (really willing to upgrade their machine twice a day with the latest horrors from MS and other sites), knowing how the situation is worsening, how us customers are we going to face with real world project requirements like deploying tailored solutions to our clients' Windows NT systems ?
-
I just stumped on this in a newsgroup : "Frustrating finding the 1.0 framework @ microsoft.com for installation on my client's server." --> For those who wouldn't get it, the guy says it's now impossible to find the .NET framework 1.0, that was until April24 the only run-time available for .NET, and was working hand-in-hand with VS.NET 2002. By removing .NET 1.0 from the download sites, MS is aggressively ensuring we upgrade to VS.NET 2003. (VS.NET 2002 exclusively uses .NET 1.0, and MS made sure with VS.NET 2003 that VS.NET 2003 would purposedly only be able to use .NET 1.1). Looks like MS does not care about customers developing 1.0 .NET projects. What fucking policy is that ? As a result, for those who would start .NET 1.1 projects from now on, what ensures them that MS does not come next year with a breaking .NET 2.0 upgrade ? All this would seem may be a bit childish if the .NET upgrades were backward compatible. Unfortunately, that's not the point : .NET components are tightly coupled with very costly VS.NET products. "Funny how when Microsoft moves on to something new, they flat abandon everything they used to go bananas over just weeks prior. When VS.NET came out, all VB6 articles completely vanished. They suck like that. I don't like it. I still have to install my October, 2000 MSDN CDs to get full legacy documentation for VS6." --> Read and learn. MS is silently removing significant topics from MSDN. The topics are removed claimwise because they are discussing plumbing. But in practice, plumbing is the very heart of Windows programming, as a whole. Experienced programmers know that a lot standard Windows programming details, techniques, protocols, know-how cannot be found anymore in MSDN since 2001, when MS decided it was 100% focusing on .NET. Another example : on September 2002 MS silently removed all Windows 9X/NT/2000 DDKs (device driver kits) from their download site, ensuring that only the latest Windows XP DDK remained available. Just in case customers would have forgotten to upgrade to Windows XP before they finished their projects dealing with DDK. So my question is : let aside technologists (really willing to upgrade their machine twice a day with the latest horrors from MS and other sites), knowing how the situation is worsening, how us customers are we going to face with real world project requirements like deploying tailored solutions to our clients' Windows NT systems ?
Stephane Rodriguez. wrote: Another example : on September 2002 MS silently removed all Windows 9X/NT/2000 DDKs (device driver kits) from their download site, ensuring that only the latest Windows XP DDK remained available. Just in case customers would have forgotten to upgrade to Windows XP before they finished their projects dealing with DDK. I think you can still get these on MSDN Subscriber Downloads.
Shameless Plug - Distributed Database Transactions in .NET using COM+
-
I just stumped on this in a newsgroup : "Frustrating finding the 1.0 framework @ microsoft.com for installation on my client's server." --> For those who wouldn't get it, the guy says it's now impossible to find the .NET framework 1.0, that was until April24 the only run-time available for .NET, and was working hand-in-hand with VS.NET 2002. By removing .NET 1.0 from the download sites, MS is aggressively ensuring we upgrade to VS.NET 2003. (VS.NET 2002 exclusively uses .NET 1.0, and MS made sure with VS.NET 2003 that VS.NET 2003 would purposedly only be able to use .NET 1.1). Looks like MS does not care about customers developing 1.0 .NET projects. What fucking policy is that ? As a result, for those who would start .NET 1.1 projects from now on, what ensures them that MS does not come next year with a breaking .NET 2.0 upgrade ? All this would seem may be a bit childish if the .NET upgrades were backward compatible. Unfortunately, that's not the point : .NET components are tightly coupled with very costly VS.NET products. "Funny how when Microsoft moves on to something new, they flat abandon everything they used to go bananas over just weeks prior. When VS.NET came out, all VB6 articles completely vanished. They suck like that. I don't like it. I still have to install my October, 2000 MSDN CDs to get full legacy documentation for VS6." --> Read and learn. MS is silently removing significant topics from MSDN. The topics are removed claimwise because they are discussing plumbing. But in practice, plumbing is the very heart of Windows programming, as a whole. Experienced programmers know that a lot standard Windows programming details, techniques, protocols, know-how cannot be found anymore in MSDN since 2001, when MS decided it was 100% focusing on .NET. Another example : on September 2002 MS silently removed all Windows 9X/NT/2000 DDKs (device driver kits) from their download site, ensuring that only the latest Windows XP DDK remained available. Just in case customers would have forgotten to upgrade to Windows XP before they finished their projects dealing with DDK. So my question is : let aside technologists (really willing to upgrade their machine twice a day with the latest horrors from MS and other sites), knowing how the situation is worsening, how us customers are we going to face with real world project requirements like deploying tailored solutions to our clients' Windows NT systems ?
You can still develop .NET v1.0 projects with VS.NET 2003, been doing it for the last two weeks now. Just have to have all those redirects in the web.config file. (Remember I do web dev so I cannot speak for Windows apps, but I assume the case is the same)
Paul Watson
Bluegrass
Cape Town, South Africabrianwelsch wrote: I find my day goes by more smoothly if I never question other peoples fantasies. My own disturb me enough.
-
I just stumped on this in a newsgroup : "Frustrating finding the 1.0 framework @ microsoft.com for installation on my client's server." --> For those who wouldn't get it, the guy says it's now impossible to find the .NET framework 1.0, that was until April24 the only run-time available for .NET, and was working hand-in-hand with VS.NET 2002. By removing .NET 1.0 from the download sites, MS is aggressively ensuring we upgrade to VS.NET 2003. (VS.NET 2002 exclusively uses .NET 1.0, and MS made sure with VS.NET 2003 that VS.NET 2003 would purposedly only be able to use .NET 1.1). Looks like MS does not care about customers developing 1.0 .NET projects. What fucking policy is that ? As a result, for those who would start .NET 1.1 projects from now on, what ensures them that MS does not come next year with a breaking .NET 2.0 upgrade ? All this would seem may be a bit childish if the .NET upgrades were backward compatible. Unfortunately, that's not the point : .NET components are tightly coupled with very costly VS.NET products. "Funny how when Microsoft moves on to something new, they flat abandon everything they used to go bananas over just weeks prior. When VS.NET came out, all VB6 articles completely vanished. They suck like that. I don't like it. I still have to install my October, 2000 MSDN CDs to get full legacy documentation for VS6." --> Read and learn. MS is silently removing significant topics from MSDN. The topics are removed claimwise because they are discussing plumbing. But in practice, plumbing is the very heart of Windows programming, as a whole. Experienced programmers know that a lot standard Windows programming details, techniques, protocols, know-how cannot be found anymore in MSDN since 2001, when MS decided it was 100% focusing on .NET. Another example : on September 2002 MS silently removed all Windows 9X/NT/2000 DDKs (device driver kits) from their download site, ensuring that only the latest Windows XP DDK remained available. Just in case customers would have forgotten to upgrade to Windows XP before they finished their projects dealing with DDK. So my question is : let aside technologists (really willing to upgrade their machine twice a day with the latest horrors from MS and other sites), knowing how the situation is worsening, how us customers are we going to face with real world project requirements like deploying tailored solutions to our clients' Windows NT systems ?
Stephane Rodriguez. wrote: --> For those who wouldn't get it, the guy says it's now impossible to find the .NET framework 1.0, After about 10 seconds of navigation, I got to this link: http://www.microsoft.com/downloads/details.aspx?FamilyId=D7158DEE-A83F-4E21-B05A-009D06457787&displaylang=en[^] Stephane Rodriguez. wrote: MS is aggressively ensuring we upgrade to VS.NET 2003. (VS.NET 2002 exclusively uses .NET 1.0, and MS made sure with VS.NET 2003 that VS.NET 2003 would purposedly only be able to use .NET 1.1). VS.NET 2003 can target 1.0 or 1.1 (it defaults to 1.1, however) -- Russell Morris "Have you gone mad Frink? Put down that science pole!"