Jump to content

Recommended Posts

Posted
This is a really good idea, but how did you get Microsoft's permission to re-distribute their software? I thought that they always wanted people to download from their website?
Posted
You could be right i haven't installed it yet.

 

I did a bit of research on this, yet I still couldn't find a definite answer! I eventually downloaded .NET Framework 3.5 and extracted it using WinRAR. It only includes .NET Framework 2.0 and 3.0 msp and msi files, so it does appear to be .NET Framework 2.0 SP1 and .NET Framework 3.0 SP1.

 

The reason .NET Framework 3.5 is so massive, is because not only does it include the above service packs, but it includes both x64 and x86 files. Why Microsoft don't make these seperate like every other download I am unsure!? To add even more complication, .NET Framework 3.5 SP1 is on the horizon too. It also appears that Visual Studio 2008 makes use of .NET Framework 3.5, so there's no immediate rush to install it as I do not use it.

 

All I can say is, what a mess Microsoft! They should just keep each version seperate in my opinion.

 

I will create a pack that it includes .NET Framework 3.5 too, probably next month when the July hotfixes are released. It's easy enough to install silently:

 

dotnetfx35.exe /quiet /passive /norestart

Posted (edited)
As you say it's not very clear and to make it even more difficult .net 2.0 SP1 is almost exactly the same size as the full version. I do remember reading on an MS blog that 3.5 contains the full versions of 2 and 3 if i find the blog i'll post it. 3.5 also contains lots of extra Vista specific jazz (Windows Presentation Foundation) to help it grow ever larger. Edited by cookie_monster
Posted
I do remember reading on an MS blog that 3.5 contains the full versions of 2 and 3 if i find the blog i'll post it.

 

Yeah that'd be good if you could. In the package I've created .NET Framework 2.0 and 3.0 with service packs comes to 98MB. If .NET Framework 3.5 does include .NET Framework 2.0 and 3.0 + SP1, then it would only add a measly 100MB extra to the overall size of the package.

Posted
Found it

 

Brilliant, thanks for that. It is .NET Framework 2.0 with SP1 and .NET Framework 3.0 with SP1 after all.

 

I think I'll strip out .NET Framework 2.0 and 3.0, but leave 1.1. .NET Framework 3.5 should be all I need then.

 

I'm proabbly getting it confused, but wouldn't the .Net Framework 3.5 compact redistributable do the job.

 

I could use this in theory, but I'm put off by the fact it's compact. Only the essential components are there but not all. I'm not a .NET Framework expert, so I don't know what exactly the differences are between the two packages. All I can say is that there's a size difference for a reason!

Posted (edited)
I still haven't been required to install .NET Framework 3.5 for any reason yet so i'd be tempted to leave it out for now then add 3.5 SP1 when it becomes available or if you come across an app that requires it that would keep the size down. But then again if you're stripping out 2.0 and 3.0 it might be worth waiting for, or you could do one package with 3.5 and one without :) decisions decisions Edited by cookie_monster
Posted

Thanks and a very good idea. I wont be using the .Net Framework side yet as its included in my Custom XP CD.

 

I also have a share on the network to AutoPatchers new updater. I have to update at home though as it doesnt support proxy's yet and bring it in on HDD. It contains all Office 2003 SP's and updates and Vista / Windows Server 2003 and now also supports Post SP3.

 

It's an unsupported release at the moment and i'm only testing it. No problems so far. Initially it downloads them all from MS. :p

Posted

What have people's experiencing been with my post XP SP3 pack? I used it again today on a new system and it worked just fine. Has anyone had any problems or any additions/ideas (excluding .NET Framework 3.5) that I could make/add?

 

The main advantage of the post XP SP3 pack is that it's a true offline package which can save a lot of time and effort.

Posted

Edited the batch file (just paths and added "shutdown -r" to the end) and have run it via a login script from a share on a server, works a treat. :hat:

 

Thanks :wave:

Posted

Glad it worked a treat! Feel free to leave thanks where credit is due ;)

 

Edited the batch file (just paths and added "shutdown -r" to the end)

 

That's a good idea, especially as you're deploying the updates :)

  • 2 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...