Lorenzo Barbieri @ Weblogs.Asp.Net

I think the problem is that adding the .NET Framework in service packs will make the SP download so much bigger that likely folks might not download the SP's (especially if SP after SP contained it...)

Doug: C'mon, do you think people matter whether the DL is 120 or 142 MB?
I certainly don't ...

I am with you, Lorenzo.
+1

I think it's based on the notion that service packs should fix bugs not provide new features.

Yes, but with new SPs (like the upcoming SP2 for XP and SP1 for W2K3), you will have new features, like the new firewall, the new automatic updates, the pop-up blocker, the outlook mail blocker, the new wireless UI, etc...

And considering that it's more than 200Mb (I hope that it's only for the beta...) the size of the .Net Fx will be less than 10%...

Even if it were included, that doesn't help because the CLR is side-by-side.

Suppose SP1 comes with version xyz of the CLR. Your program uses version xyz of the CLR. Now SP2 comes with version xyz+3 of the CLR. Oops, your program listed xyz in its manifest and xyz != xyz+3. So you have to include a copy of CLR version xyz with your program anyway.

Raymond, I agree with you, perhaps I'm only complaining that is still very difficult to distribute apps for the .NET Framework today.
I know for example that with Windows XP I have MDAC 2.7, and I know that if I need MDAC 2.8 I've to redistribute it, but if I don't need it, I can assume that it is there (and perhaps that it will be updated in next service packs)...
I want to know what will happen with the first SP for W2k3? It will include the SPx of .Net 1.1 (if it's available)? It's a separate download? For me .Net 1.1 is a part of the OS, like explorer, outlook express or the media player...

Sorry, in the last sentence I supposed to write "is a part of THAT OS"...

The MDAC example is different because MDAC isn't side-by-side. There is only one MDAC on the system. If it's greater than or equal to the version you want, then you get it. If the new version isn't 100% backwards-compatible with the old version, then your program crashes and you can't do anything about it.

This is the source of DLL hell: Program A wants version x of MDAC, but program B wants version y of MDAC, and there's only one MDAC so something's gotta give; somebody is going to lose.

The CLR is side-by-side. When you specify that "my program wants version xyz of the CLR" that's what you get. If there's a newer version, you don't get it because that's not what you asked for. This finesses the compatibility issue. You get only the version you wanted. There are no surprises, no DLL hell. Everybody gets exactly the CLR they want.

(Yes, an assembly can mark itself as "I am 100% compatible with this other version, you can use me as a replacement for it and I absolutely guarantee that there will be no problems" but that's the exception rather than the rule.)