. NET Framework 1.1 SP1:
Http://www.microsoft.com/downloads/details.aspx? Displaylang = ZH-CN & familyid = A8F5654F-088E-40B2-BBDB-A83353618B38
. NET Framework 1.1 SP1 for win2003:
Http://www.microsoft.com/downloads/details.aspx? Displaylang = ZH-CN & familyid = AE7EDEF7-2CB7-4864-8623-A1038563DF23
. NET Framework 1.0 SP3:
Http://www.microsoft.com/downloads/details.aspx? Familyid = 6978d761-4a92-4106-a9bc-83e78d4abc5b & displaylang = en
Finally, some code samples of Some. NET Framework 2.0 beta1:
Http://www.microsoft.com/downloads/details.aspx? Familyid = c3c41e75-f8a8-4077-84cf-e43176d93b1e & displaylang = en
In addition, we all know that Ms has decided to enable aveon and indigo to run on WINXP and win2003, winfs is removed from the Longhorn release (which will be provided in a form similar to add-on later ). The most common problem I have seen on the internet is that since aveon and indigo can already be used on WINXP, and there is no winfs in Longhorn, so what is the reason for upgrading WINXP to Longhorn? Well, it's an interesting question...