Onepiece's Microsoft .NET Framework 1.1 SP1 - 2.0 SP2 - 3.0 SP1 - 3.5 SP1 with hotfixes TRUE Addons for Windows XP and Windows 2003

 

.net 1.1 SP1 full (includes all public GDR updates):

OnePiece Microsoft.NET Framework v1.1.4322.2503 True AddOn ENU
Update (July 10 2013)
Update (July 10 2013)
Update (July 10 2013)
Update (July 10 2013)
Hash MD5 18A2C471618924589568631E4F7BB4EB
Filesize: 12.7 MB (13,380,330 bytes)

 

.net 2.0 SP2 full (includes all public GDR updates):

OnePiece Microsoft.NET Framework v2.0.50727.8763 True AddOn ENU
Update (22 June 2017)
Update (22 June 2017)
Update (22 June 2017)
Hash MD5 8C794335B0EB92E874F517B31000256E
Filesize: 21.04 MB (22059180 bytes)

 

.net 3.0 SP1 full (includes 2.0 and all public GDR updates):

OnePiece Microsoft.NET Framework v3.2.30729.8774 True AddOn ENU
Update (22 June 2017)
Update (22 June 2017)
Update (22 June 2017)
Hash MD5 7F70ED261655B34BE591A5FDF478A071
Filesize: 33.86 MB (35505060 bytes)

 

.net 3.5 SP1 full (includes 2.0 and 3.0 with all public GDR updates):

OnePiece Microsoft.NET Framework v3.5.30729.4056.11 True AddOn ENU
Update (22 June 2017)
Update (22 June 2017)
Update (22 June 2017)
Hash MD5 89B1355B77D91A23833C6DA518A4779A
Filesize: 39.16 MB (41065196 bytes)

 

The peculiarity of these addons is that .NET framework is directly slipstreamed into your XP/2003 source, without the need of running .msi files or svcpack/runonce installations, a true addon integration just like .net 1.0 in Windows Server 2003.
So you will get a working .NET framework already installed BEFORE T-13 (svcpack time), a very handy opportunity.

The addons are cumulative: you must integrate only the one you need. They include all the publicly released hotfixes at the present date.

If you use Onepiece's XP postSP3 AIO Update Pack or W2k3 postSP2 AIO Update Pack you do not need these addons because they are already included.

Unlike other Onepiece's true addons, here updates GDR branch is used. This because in dotnet updates MicrosoftUpdate forces GDR over QFE branch, which always has an higher build, so this cause the update installation to fail with repeated and annoying attempts.
If someone despite that still wants a QFE updated full .Net true integration, here is an additional addon for 3.5 SP1 which adds QFE branch public updates over GDR ones added by Onepiece's addon. Obviously it works only combined with .NET v3.5 true addon.
 

 

OnePiece Microsoft.NET Framework v3.5.30729.7056.11 QFE Update AddOn

Update (22 June 2017)
Update (22 June 2017)
Update (22 June 2017)
Hash MD5 2232D5C7AA3F46AE9C19E45C2F026A5A
Filesize: 17.12 MB (17951297 bytes)

 

All .Nets can be unistalled from Windows Component Wizard:
 


You can also force .net removal typing one of these command in a Run window:
 

RUNDLL32.exe advpack.dll,LaunchINFSection NETFX20.inf,NETFX20.SHOW

RUNDLL32.exe advpack.dll,LaunchINFSection NETFX20.inf,NETFX20.HIDE

RUNDLL32.exe advpack.dll,LaunchINFSection NETFX20.inf,NETFX20.CleanUp

NETFX20.SHOW: shows DotNetXX in Windows Component Wizard (default)
NETFX20.HIDE: hides DotNetXX in Windows Component Wizard
NETFX20.CleanUp: executes a forced cleanup of DotNetXX Setup from Windows registry so you can reinstall DotnetXX again from a common installer file.

 

How to update the DotNet True AddOn

Edited June 22, 20177 yr by nonno fabio

thanx :thumbsup_anim:

Amazing release

***TOP WORK***

Thanks . Just a quick question.

I'm trying your package: .net 3.5 SP1 full (includes 2.0 and 3.0) in HFSLIP.

I don't see it listed in Add/remove Panel or Optional component. Is this correct?

That's correct. None of the .net installers from onepiece will be listed in add/remove programs. That's by design.

I don't agree with that philosophy.

But that is how onepiece wants it.

They aren't in Add/Remome Programs (or better in Windows components) because Onepiece got no time to fully test the uninstallation.

They are ready to be listed in WCW: if you remome HIDE from this line in Windows registry

netfx40=ocgen.dll,OcEntry,netfx40.inf,hide,7

you'll get this even now

http://img97.imageshack.us/img97/8659/cattura22.png

but since they aren't uninstallable at this moment, there's no reason to uncover them in WCW

Mr_Smartepants, nonno fabio thanks for the reply.

While I dun expect uninstall functionality, it is certainly useful to have it listed somewhere (like WCW). Thanks for the tips! I will try that.

Having .NET ready b4 T13 certainly have an advantage (and an easier time) when installing other .NET-dependant programs via svcpack. I can convert most of my RunOnceEx program to svcpack installation.

Hi, just to feedback Automatic Updates is saying I'm missing KB961118 after I did a clean install.

FYI: I'm using OnePiece_Microsoft.NET_Framework_v3.5.30729.196_True_AddOn_ENU.cab with HFSLIP

updated with latest critical updates

Thanks a lot. They work well with HFSLIP.

Thank You

ขอบคุณมากครับ

New releases with 2.0-3.5 updates and major improvements related to .net updating.

Furthermore now .Nets are uninstallable from Add/Remove Windows Components

Thank You nonno fabio. Great work! :thumbsup_anim:

Furthermore now .Nets are uninstallable from Add/Remove Windows Components

Wow, that is great news! Thank you.

Hi OnePiece

First, thanks for your true addon with uninstall capability. This is indeed a magnificent work.

Below are some queries that, by no mean on my part, diminish your great work and effort. Just some observation that hope you can help to clarify.

(Below queries are all reference to your package dated June 28-2010)

Refering to NETFX20.INF, from line 7378 to 7752, there are lots of registry value that are hardcode to C:\

Some even of E:\ (e.g line 7561,7580,7748)

Refering to NETFX30.INF, from line 852 to 890, this is also the same.

Refering to NETFX35.INF, from line 509 to 549, this is also the same.

But from and 634 to 881, there are a mixture of c:\, c?\, %10% and 16422%.

Are these some kind of conversion error?

Can these be converted to environmental variable, like %24%?

My concern is : If we install xp with .NET_Framework_v3.5.30729.196 integrated, and on a harddrive that is not C: drive, will .NET_Framework_v3.5.30729.196 work properly?

Put simply, if install on D drive, will there be any problem? Assuming C: drive is another OS like Win7.

(You know, nowsadays, most of newer laptop comes with W7. Hence if we want to install on XP on 2nd partition, will these codes affect C partition)

Best regards

Hi OnePiece

First, thanks for your true addon with uninstall capability. This is indeed a magnificent work.

Below are some queries that, by no mean on my part, diminish your great work and effort. Just some observation that hope you can help to clarify.

(Below queries are all reference to your package dated June 28-2010)

Refering to NETFX20.INF, from line 7378 to 7752, there are lots of registry value that are hardcode to C:\

Some even of E:\ (e.g line 7561,7580,7748)

Refering to NETFX30.INF, from line 852 to 890, this is also the same.

Refering to NETFX35.INF, from line 509 to 549, this is also the same.

But from and 634 to 881, there are a mixture of c:\, c?\, %10% and 16422%.

Are these some kind of conversion error?

Can these be converted to environmental variable, like %24%?

My concern is : If we install xp with .NET_Framework_v3.5.30729.196 integrated, and on a harddrive that is not C: drive, will .NET_Framework_v3.5.30729.196 work properly?

Put simply, if install on D drive, will there be any problem? Assuming C: drive is another OS like Win7.

(You know, nowsadays, most of newer laptop comes with W7. Hence if we want to install on XP on 2nd partition, will these codes affect C partition)

Best regards

It's all OK. Those registry values are related to .net uninstall only, used because .inf file can't write registry in Windows Installer mode. There will be no issue with .nets if you install XP on a drive different than C:

Thanks, nice to know this

Hey nonno. You wrote ".net 3.5 SP1 full (includes 2.0 and 3.0)".

Does it mean, that .net 3.5 SP1 full includes 2.0 SP2 and 3.0 SP1 too ?

// Edit:

Ok, I checked files, and now I see all

Thanks for addon

Edited July 15, 201014 yr by pietreXtreme

Updated.

1.1: improved compatibility with XP MCE 2005

2.0-3.0-3.5: added NDP20SP2-KB983583-x86

New releases. Now updates GDR branch is used. This because in dotnet updates MicrosoftUpdate forces GDR over QFE branch, which always has an higher build, so this could cause MU/WU to fail with repeated and annoying attempts.

Anyway for the braves who despite that still want a full QFE branch updated .net true integration there's also an additional addon to overwrite GDR updated files added by Onepiece's 3.5 SP1 GDR true addon with QFE ones

nice work with those frame work addons..

any chance of you making a all in one 1.1 - 40 true addon all in one package please

nice work with those frame work addons..

any chance of you making a all in one 1.1 - 40 true addon all in one package please

An all-in-one addon composed by 1.1+3.5full+4.0 is useless because you don't save any space and anyway each dotnet framework must wait the setup end of previous one before it can start its one, as in 3 separate addon like now.

ykchanaed said

An all-in-one addon composed by 1.1+3.5full+4.0 is useless because you don't save any space and anyway each dotnet framework must wait the setup end of previous one before it can start its one, as in 3 separate addon like now.

its ok ive found a way to add 1.1 - 3.5 and 4.0 frameworks..

and it works great..

framework 1.1 - 3.5 addon

http://www.ryanvm.net/forum/viewtopic.php?t=8236

framework 4.0 addon

http://www.ryanvm.net/forum/viewtopic.php?t=8229

My question is: where in hfslip I have to put file OnePiece_Microsoft.NET_Framework_v3.5.30729.196.2_True_AddOn_ENU.cab?

The addon should be placed in HFAAO folder.