Microsoft .NET Framework 3.5 Service Pack 1

For sysadmins that have dared to upgrade their machines past the .NET 2.0 Framework, the .NET 3.5 Service Pack 1 is now available.

Let the pigeons loose!!

Find more posts tagged with

Free for TechExams community: Cybersecurity salary guide

Compare cert salaries and plan your next career move

Button

Comments

dynamik

Yea, I had to install that in order to get SQL Server Express 2008 to work. It kept complaining that I didn't have .NET 2.0 SP2 installed (there's no such thing, only SP1).

JDMurray

There is a .NET Compact Framework 2.0 Service Pack 2 for mobile devices, but not an SP2 release for the standard distribution of .NET 2.0. MS never bothered to roll all the post-SP1 .NET 2.0 updates into an SP2.

dynamik

Yea, and that confused me even more

It was just an incorrect error message.

I'm not a developer, so I don't keep up with them nearly as much as you do. I typically only install them as needed.

blargoe

Already? 3.5 just came out!

I've been putting 3.5 on all my machines because the installer contains the installers for every prior .net framework for both x86 and x64 including service packs - a big time saver when you need 2.0 and 3.0.

techimaster

Theres no harm in putting the latest version of the .net framework on your machines. All .net applications specifically target the version of the framework they need. Each subsequent version simply adds to the previous framework. Thank god for .net, who can with stand the COM pain any longer!!

JDMurray

blargoe wrote:

Already? 3.5 just came out!

If just to you is nine months ago then, yes, .NET 3.5 and VS.NET 2008 just came out.

techimaster wrote:

Theres no harm in putting the latest version of the .net framework on your machines.

Please tell that to some of my customers who will not update their servers from .NET 2.0 because they don't want toooo!!!!

techimaster wrote:

Thank god for .net, who can with stand the COM pain any longer!!

I hate to burst your bubble, but much of the .NET Framework is just a thin shim over the existing Windows COM objects (a Microsoft perestroika of sorts). I write C# apps, but I suffer with the problems of the underlying COM objects almost on a daily basis.