Thanks for your answers, Gis.
--
Joe Davis
"Gis Bun" wrote:
> Regarding installing 3.5, it does build on 3.0 and 2.0 (and includes both
> SP1s) *but* it's no point in installing 3.5 unless you have applications that
> use it. v3.5 is based on Visual Studio 2008 applications and that alone just
> barely got released last month.
>
> My suggestion is that until an app requires it, hold off (that and it
> reduces any security issues).
>
> "Joe" wrote:
>
> > Thanks for the effort, Gis.
> >
> > I checked the KB articles relating to both .NET 2 & .NET 3 SP1s. In both
> > cases the KB# names of the updates were not mentioned, only descriptions of
> > the specific problems that were addressed/fixed.
> >
> > As for whether or not I should install .NET 3.5, sorry but "If it ain't
> > broken, don't fix it" is not the kind of answer I was looking for. .NET 3.5
> > builds om the many foundations introduced in .NET 3 & includes SP1 for both
> > .NET 2 & .NET 3; however, I am not a developer & thus wonder if I'll ever
> > need the improved structural framework.
> >
> > Cheers
> >
> > --
> > Joe Davis
> >
> >
> > "Gis Bun" wrote:
> >
> > > Usually the KB can tell you what's included in the SPs. The updates should be
> > > there.
> > >
> > > As for Installing 3.5, unless an application calls for it, you don't need to
> > > waste space on it [and possible future additional security updates]. "If it
> > > ain't broken, don't fix it."
> > >
> > > "Joe" wrote:
> > >
> > > > Does .NET 2.0 SP1 include previous updates (i.e., published 7-11-2006,
> > > > 10-10-2006, & 7-10-2007)? And does .NET 3.0 SP1 include update published
> > > > 4-12-2007?
> > > >
> > > > Also, would it be advisable for me to download & install .NET 3.5 on a WXP
> > > > Professional home compiter?
> > > >
> > > > Thanks for your help.
> > > > --
> > > > Joe Davis
|