.Net framework 3.0 SP1 Full package is not available to download - by gbodar

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


0
0
Sign in
to vote
ID 404036 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 1/22/2009 3:57:40 PM
Access Restriction Public

Description

.Net framework 3.0 SP1 Download 
http://www.microsoft.com/downloads/details.aspx?familyid=EC2CA85D-B255-4425-9E65-1E88A0BDB72A&displaylang=en

Doesnt provide link for full pacakge. If somebody wants to download the whole package and send it to Lock down machine where internet is not available, it wont be possible
Sign in to post a comment.
Posted by Microsoft on 4/30/2009 at 12:34 PM
.NET 3.5 and 3.5 sp1 were the only servicing vehicles for Vista/Win2k8.

Some more background overall on the .NET releases:

The reason for this is the underlying updates to the .NET Framework 2.0/3.0 subcomponents have interdependencies, updates also ship in the Vista/Win2k8 OS service packs, and because the full product really is .NET 3.5 and 3.5 sp1.
.NET 2.0/3.0/3.5 sp1 are not side-by-side framework releases but rather iterative feature layer additions to maximize compatability while adding features.
There were servicing updates for .NET 2.0/3.0 for Vista/Win2k8 SP1 which effectively bring it up to the .Net 2.0/3.0 "sp1" level, and likewise for Vista/Win2k8 SP2 to bring them up to the .NET 2.0/3.0 "sp2" level. As OS component updates, those are not referred to as service packs but rather component updates, but the integration and release timing does equate to when the noted pre-Vista OS "sp" vehicles were released for .NET.
The current recommended servicing level for customers is .NET framework 3.5 sp1. As a side note worth mentioning,there are a few migration issues in moving from pre-Vista to Vista/Win2k8 OS which are resolved by uninstall/re-install for 3.5 sp1 after an OS upgrade. The reason for those issues are due to the use of different deployment technologies between pre-Vista and Vista/Win2k8 for .NET and inclusion within the OS itself.

Hope this helps with a better understanding of the .NET release vehicles and relationship within the .NET product itself.

Posted by Microsoft on 1/26/2009 at 5:55 PM
Thanks for your feedback.

We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you,
Visual Studio Product Team