.NET Framework Addon Pack
James
16 Oct 2008
.NET Framework Addon Pack
General Information
This is an Addon module that you can add to the main AutoPatcher for Windows releases.
This module is displayed for selection on APUP's release selection screen.
What's Included
Microsoft .NET Framework 3.5 Service Pack 1 (Full Package)[indent]The .NET Framework 3.5 Service Pack 1 includes: .NET Framework 3.0 Service Pack 2 and .NET Framework 2.0 Service Pack 2[/indent]
Microsoft .NET Framework 2.0 Service Pack 1
Size Information
~482 MB
Supported Operating Systems
.NET Framework 3.5 SP1: Windows Server 2003; Windows Vista; Windows Vista 64-bit Edition; Windows XP; Windows XP 64-bit
.NET Framework 2.0 SP1: Windows 2000 Professional
changelog
[indent]# 29/01/2009: (Cristiano) +KB958481 (XP,2K3); +KB958483(XP,2K3); +KB958484(XP,2K3)
# 29/01/2009: (Cristiano) +KB958481 (XP,2K3); +KB958483(XP,2K3); +KB958484(XP,2K3)
# 2009/06/20: (Cristiano) +KB961118 (XP)
# 2009/06/24: (Cristiano) +KB963707
# 2009-10-17: (Cristiano) +KB953297; KB974417
# 2009-10-20: (Cristiano) NDP1.1sp1-KB953297.apm was having the undesireable effect of an reboot if aplied. fixed
# 2009-10-24: (Cristiano) added dependency to .net 1.1 to NDP1.1sp1-KB953297.apm
# 2009-12-16: (Cristiano) +KB976126; ~updated description in italian for KB963707
# 2009-12-21 Cristiano) -KB976126 (due removal of ms servers)
# 2010-01-29: (Cristiano) +KB976126 v2
# 2010-03-14: (Cristiano) +KB976569 (x86); +KB976570(x86)
# 2010-03-28: (Cristiano) fixed descripton and webpage for KB976570
# 2010-04-17: (Cristiano) +.net 4
# 2010-04-18: (Cristiano) edited NDP20SP2-KB974417.apm
# 2010-05-12: Cristiano) +KB982306
# 2010-06-10: (Cristiano) +KB982168; +KB979909; +KB979906
# 2010-06-15: (Cristiano) .net package consolidation; updated detections for several modules
# 2010-06-24: (Cristiano) +KB977354; updated __dotnet.apm
# 2010-06-25: (Cristiano) -KB977354; +KB982524 (rollup KB976576 + KB977354)
# 2010-08-11: (Cristiano) -KB974417; +KB983583
# 2010-08-19: (Cristiano) -KB976569
# 2010-09-28: (Cristiano) +KB2416472; +KB2416473; +KB2418241; +KB2416447; -KB979906
# 2010-09-29: (Cristiano) +KB2416471; +KB2416470
# 2010-09-30: (Cristiano) +KB2416472-x64; +KB2416471-x64
# 2010-10-06: (Cristiano) ~Windows6.1-KB2416471-x64.apm
# 2010-10-14: (Cristiano) +KB2160841; KB2416472 restricted to .net 4 full
[/indent]
note: Dates are in YYYYMMDD format
the script now will download an md5 checksum for the modules, like this one md5_checksum_for_DotNet_Addon_Pack.md5
just one double-click and, if yours have an md5 tool like hksfv or similar, will be far more easy check for issues related to unofficial versions
[]s
The AutoPatcher Team
Edited by Cristiano, 14 October 2010 - 09:28 PM.
General Information
This is an Addon module that you can add to the main AutoPatcher for Windows releases.
This module is displayed for selection on APUP's release selection screen.
What's Included
Microsoft .NET Framework 3.5 Service Pack 1 (Full Package)[indent]The .NET Framework 3.5 Service Pack 1 includes: .NET Framework 3.0 Service Pack 2 and .NET Framework 2.0 Service Pack 2[/indent]
Microsoft .NET Framework 2.0 Service Pack 1
Size Information
~482 MB
Supported Operating Systems
.NET Framework 3.5 SP1: Windows Server 2003; Windows Vista; Windows Vista 64-bit Edition; Windows XP; Windows XP 64-bit
.NET Framework 2.0 SP1: Windows 2000 Professional
changelog
[indent]# 29/01/2009: (Cristiano) +KB958481 (XP,2K3); +KB958483(XP,2K3); +KB958484(XP,2K3)
# 29/01/2009: (Cristiano) +KB958481 (XP,2K3); +KB958483(XP,2K3); +KB958484(XP,2K3)
# 2009/06/20: (Cristiano) +KB961118 (XP)
# 2009/06/24: (Cristiano) +KB963707
# 2009-10-17: (Cristiano) +KB953297; KB974417
# 2009-10-20: (Cristiano) NDP1.1sp1-KB953297.apm was having the undesireable effect of an reboot if aplied. fixed
# 2009-10-24: (Cristiano) added dependency to .net 1.1 to NDP1.1sp1-KB953297.apm
# 2009-12-16: (Cristiano) +KB976126; ~updated description in italian for KB963707
# 2009-12-21 Cristiano) -KB976126 (due removal of ms servers)
# 2010-01-29: (Cristiano) +KB976126 v2
# 2010-03-14: (Cristiano) +KB976569 (x86); +KB976570(x86)
# 2010-03-28: (Cristiano) fixed descripton and webpage for KB976570
# 2010-04-17: (Cristiano) +.net 4
# 2010-04-18: (Cristiano) edited NDP20SP2-KB974417.apm
# 2010-05-12: Cristiano) +KB982306
# 2010-06-10: (Cristiano) +KB982168; +KB979909; +KB979906
# 2010-06-15: (Cristiano) .net package consolidation; updated detections for several modules
# 2010-06-24: (Cristiano) +KB977354; updated __dotnet.apm
# 2010-06-25: (Cristiano) -KB977354; +KB982524 (rollup KB976576 + KB977354)
# 2010-08-11: (Cristiano) -KB974417; +KB983583
# 2010-08-19: (Cristiano) -KB976569
# 2010-09-28: (Cristiano) +KB2416472; +KB2416473; +KB2418241; +KB2416447; -KB979906
# 2010-09-29: (Cristiano) +KB2416471; +KB2416470
# 2010-09-30: (Cristiano) +KB2416472-x64; +KB2416471-x64
# 2010-10-06: (Cristiano) ~Windows6.1-KB2416471-x64.apm
# 2010-10-14: (Cristiano) +KB2160841; KB2416472 restricted to .net 4 full
[/indent]
note: Dates are in YYYYMMDD format
the script now will download an md5 checksum for the modules, like this one md5_checksum_for_DotNet_Addon_Pack.md5
just one double-click and, if yours have an md5 tool like hksfv or similar, will be far more easy check for issues related to unofficial versions
[]s
The AutoPatcher Team
Edited by Cristiano, 14 October 2010 - 09:28 PM.
Cristiano
29 Jan 2009
i've updated the .net script to include like following:
changelog:
# 29/01/2009: (Cristiano) +KB958481 (XP,2K3); +KB958483(XP,2K3); +KB958484(XP,2K3) (all those are x86 only)
i know that there's an version of those kbs to Windows Vista and Windows Server 2008, but i don't have those and i can't take proper detections and install strings for this ones. so, i'm really sorry, but i will have to leave those for now. if someone have access to those and can take proper detections and install strings, i can update the script again to math. if i'm not mistaken, those updates can be found in here
the script was left unsigned, but i'm downloading all those in order to be able to sign the modules. i know that those updates are working, because i'm running those modules into my own script since about 1 month ago, but if someone had any trouble with, please report
[]s and sorry for the delay
changelog:
# 29/01/2009: (Cristiano) +KB958481 (XP,2K3); +KB958483(XP,2K3); +KB958484(XP,2K3) (all those are x86 only)
i know that there's an version of those kbs to Windows Vista and Windows Server 2008, but i don't have those and i can't take proper detections and install strings for this ones. so, i'm really sorry, but i will have to leave those for now. if someone have access to those and can take proper detections and install strings, i can update the script again to math. if i'm not mistaken, those updates can be found in here
the script was left unsigned, but i'm downloading all those in order to be able to sign the modules. i know that those updates are working, because i'm running those modules into my own script since about 1 month ago, but if someone had any trouble with, please report
[]s and sorry for the delay
darthyoda6
02 Aug 2009
Out of curiosity, shouldn't .net 1 sp 1 & .net 3.5 be dependent on .net 1 being installed first, or does it not matter?
Cristiano
02 Aug 2009
doesn't matter. the install dates for this ones set 1.1 to be installed before the others, if selected to install. but if the user chooses to install 3.5 before 1.1, the only issue that he will have is an security issue, but 1.1 still will install after that
[]s
[]s
James
02 Aug 2009
@ darthyoda6
Cristiano is right, it doesn't matter for the early .NET products.
Very briefly:
.NET 1.0 .NET 1.1 and .NET 2.0 can all be installed side-by-side, because there is no dependency.
However,
.NET 2.0 .NET 3.0 and .NET 3.5 all depend on each other and MUST be installed in forward order and uninstalled in reverse order.
==
Cristiano is right, it doesn't matter for the early .NET products.
Very briefly:
.NET 1.0 .NET 1.1 and .NET 2.0 can all be installed side-by-side, because there is no dependency.
However,
.NET 2.0 .NET 3.0 and .NET 3.5 all depend on each other and MUST be installed in forward order and uninstalled in reverse order.
==
DesertJerry
02 Aug 2009
And for all those really paying attention the .NET 4.0 is also available, though still in beta for now.
Not sure if it's dependent on any earlier version as I had them installed already when I installed 4.0 - actually listed on my system as v4.0.20506
Not sure if it's dependent on any earlier version as I had them installed already when I installed 4.0 - actually listed on my system as v4.0.20506
_def_x_
18 Oct 2009
...minor edit needed to autopatcher_dotnet_20091017.script
Re: Item=NDP1.1sp1-KB953297-X86.exe
DetectFile=autopatcher:\modules\Components\__dotnet\NDP1.1sp1-KB953297.apm_files\NDP1.1sp1-KB953297-X86.exe
DownloadTo=autopatcher:\modules\Components\__dotnet\NDP1.1sp1-KB953297_files\NDP1.1sp1-KB953297-X86.exe
Re: Item=NDP1.1sp1-KB953297-X86.exe
DetectFile=autopatcher:\modules\Components\__dotnet\NDP1.1sp1-KB953297.apm_files\NDP1.1sp1-KB953297-X86.exe
DownloadTo=autopatcher:\modules\Components\__dotnet\NDP1.1sp1-KB953297_files\NDP1.1sp1-KB953297-X86.exe
Cristiano
18 Oct 2009
done. it's always the small and silly things... no new download shall be need. the .net script will rename the folder to his proper name
thanks
[]s
Edited by Cristiano, 18 October 2009 - 10:56 AM.
thanks
[]s
Edited by Cristiano, 18 October 2009 - 10:56 AM.
_def_x_
18 Oct 2009
Cristiano said:
done. it's always the small and silly things
Cristiano
21 Oct 2009
NDP1.1sp1-KB953297.apm was rebooting the machine after applied. fixed
[]s
[]s
_def_x_
25 Oct 2009
Interesting! I noticed this in the APUP log...
Missing file G:\AutoPatcher\Addons.Misc\bin\Mswinsck.ocx Item AutoPatcher Runtime (bin folder) is missing. Adding its download to the queue.Is this a new addition to the \bin folder, I don't remember seeing Mswinsck.ocx in any other folder than \apup_bin?
Cristiano
25 Oct 2009
i've noticed that this file was in the old scripts, but have vanished in some way. i'm unsure if this file is really required for autopatcher.exe, but i've included this one anyway, just in case
[]s
[]s
Cristiano
20 Dec 2009
for those concerned about an fail in the .net script, this isn't related to an fail in the software. that is an fail in ms servers. ms has released NDP35SP1-KB976126-x86.exe a few days ago and this one is already replaced. take a look in here
so, that is an ms issue, not ours. as soon they fix the issue, the script will work fine again
[]s
Quote
Overview
Due to an unforeseen issue the ADO.NET Data Services Update for the .NET Framework 3.5 SP1 is not currently available for download. The team is working on a fix for the issue and will make a new version of this update available as soon as possible. We apologize for any inconvenience.
Due to an unforeseen issue the ADO.NET Data Services Update for the .NET Framework 3.5 SP1 is not currently available for download. The team is working on a fix for the issue and will make a new version of this update available as soon as possible. We apologize for any inconvenience.
so, that is an ms issue, not ours. as soon they fix the issue, the script will work fine again
[]s
Dibakar
06 Feb 2010
KB892130: Windows Genuine Advantage Validation Tool
KB905474: Windows Genuine Advantage Notifications
What this two updates do..???Does it checks whether the installed Operating System is genuine..??
KB905474: Windows Genuine Advantage Notifications
What this two updates do..???Does it checks whether the installed Operating System is genuine..??
Cristiano
06 Feb 2010
well, those updates are in the extras package, not at the ,net. but ok. according to ms, booth updates aim warn the user about the status of their OS, informing the user if the OS is genuine and, if not, provide an way to the user buy an version. also, one of those updates may show to the user the advantages of being running an genuine OS
[]s
[]s
DesertJerry
15 Feb 2010
Just ran APUP - 15 Feb 2010 1450 hours (California)
Microsoft Windows > Updated Components - there is no listing for: dotNetFx40_Client_x86.exe or dotNetFx40_Client_x86_x64.exe or dotNetFx40_Full_x86.exe or dotNetFx40_Full_x86_x64.exe all of which were released 10 Feb 2010
Microsoft Windows > Updated Components - there is no listing for: dotNetFx40_Client_x86.exe or dotNetFx40_Client_x86_x64.exe or dotNetFx40_Full_x86.exe or dotNetFx40_Full_x86_x64.exe all of which were released 10 Feb 2010
_def_x_
16 Feb 2010
@DesertJerry
I'm not sure .Net Framework 4.0 is ready for primetime, I believe it is a preview release -> 4.0.30128.1 / 4 (RC1)
I'm not sure .Net Framework 4.0 is ready for primetime, I believe it is a preview release -> 4.0.30128.1 / 4 (RC1)
Cristiano
16 Feb 2010
all those seems to be beta 2, at least according to this. when those reach the rtm version, they will be included, most likely dotNetFx40_Full_x86_x64.exe, but will
but none beta is included
[]s
but none beta is included
[]s


