|
|
|
date: Wed, 13 Aug 2008 10:17:57 -0700 (PDT),
group: microsoft.public.dotnet.framework
back
Re: Confused about 3.5 SP1
Alex Clark <quanta@noemail.noemail> wrote:
> > To be honest, having seen some of the stuff in SP1, it feels more like
> > a 3.6 than a genuine service pack...
>
> Well, to give it it's correct version notation, it should really be called
> .NET 2.3.
>
> v3.0 was really 2.1, v3.5 was really 2.2, and the new bangs and whistles
> this SP adds push it up to 2.3. At its core it is still, of course, 2.0
> with some nice addons.
>
> Weird way to version it if you ask me...
I would personally have called 3.0 => 2.5 and 3.5 => 3.0. There are
enough new features (including *language* features) to merit a major
bump at that point, IMO - I don't think there's a need to keep parity
between CLR and Framework version, for instance.
The fact that core libraries were amended and added to makes it a
bigger version change than the straight additions from 2.0 to 3.0.
--
Jon Skeet -
Web site: http://www.pobox.com/~skeet
Blog: http://www.msmvps.com/jon.skeet
C# in Depth: http://csharpindepth.com
date: Wed, 13 Aug 2008 21:43:39 +0100
author: Jon Skeet [C# MVP]
Re: Confused about 3.5 SP1
If you are not using the new stuff (ADO.NET Entitities, AJAX enhancements,
routing, dynamic data, data services, etc.), then the app can work fine on
the client machines without SP1. There are also fixes in the SP, but you
have to decide how much "pain" you need at this time. I would imagine this
SP will be a suggested update on Windows Update at some time and they will
update then.
As far as "is there a reason" is concerned, I have not looked at a list of
fixes in the SP, so I cannot definitively give a reason to update now.
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
Subscribe to my blog
http://feeds.feedburner.com/GregoryBeamer#
or just read it:
http://feeds.feedburner.com/GregoryBeamer
********************************************
| Think outside the box! |
********************************************
wrote in message
news:fa6330ff-8290-47be-b5db-2d6ff519860f@z6g2000pre.googlegroups.com...
> I've installed VS2008 SP1 with .net Framework 3.5 SP1 on my
> development machines... The apps I'm building (or rebuilding) seem to
> run fine on client machines that are at 3.5. Is there a reason to
> install 3.5SP1 on the users machines?
>
> Bob
date: Thu, 14 Aug 2008 07:54:50 -0500
author: Cowboy \(Gregory A. Beamer\) oSpamM
Re: Confused about 3.5 SP1
On Aug 14, 12:05 am, Jon Skeet [C# MVP] wrote:
> sloan wrote:
> > I guess I consider contract breaks meaning code you have right now, won't
> > compile in SP1.
>
> That way is fine - although not strictly accurate in this case. I
> believe there's at least one bug which was fixed in SP1 which would
> previously have allowed code which shouldn't work to work. I can't find
> the link now, but basically listOfInts.Cast<float>() would have been
> okay before, but will now throw an exception when you try to iterate
> through it.
Here's the link:
http://blogs.msdn.com/ed_maurer/archive/2008/02/16/breaking-change-in-linq-queries-using-explicitly-typed-range-variables.aspx
Basically, they've used IConverter in Enumerable.Cast before, so you
could do some value-type conversions using it as well - such as float-
>int - but the semantics of those were different from C# casts. In
SP1, they've changed it to use a plain C# cast, which means that value
conversions won't work anymore, only the usual object reference
upcasting/downcasting.
I wish they've introduced an argumentless Enumerable.Convert() to
provide the old behavior on explicit request, though.
date: Thu, 14 Aug 2008 06:19:50 -0700 (PDT)
author: Pavel Minaev
|
|
