Relationship between versions of .Net Framework



I am developing an application using Visual Studio 2005, Windows XP
(or 2003) and C#. I am using facilities of .Net Framework 3.0, but not
of 3.5.

I am falling foul of some memory leaks in the framework, which
Microsoft claim to have fixed in .Net Framework 3.5 SP1.

I confess to not really understanding how the various versions of .Net
Framework that have been installed on my machines are actually used by
the application.

So my question is: if the leaks really are fixed in 3.5 SP1, will
installing that service pack also fix the same leaks in 3.0?

(Of course, only the Beta of 3.5 SP1 is currently available, but I
could be brave and try it).
.



Relevant Pages

  • Re: Relationship between versions of .Net Framework
    ... Framework that have been installed on my machines are actually used by ... installing that service pack also fix the same leaks in 3.0? ... SP1 actually installs all ... Microsoft claim to have fixed in .Net Framework 3.5 SP1. ...
    (microsoft.public.dotnet.framework)
  • Re: Relationship between versions of .Net Framework
    ... your application can only run one version of the .NET framework at execution time. ... > installing that service pack also fix the same leaks in 3.0? ... Don't install 3.5 SP1 if you haven't tested the previous SPs for earlier frameworks. ... I'll take a peak at the complete of bug fixes in 3.5 SP1 to see if any deal with imaging memory leaks. ...
    (microsoft.public.dotnet.framework)
  • Re: XPe and Framework 1.1. SP1 : wont install
    ... I resolved it by installing .Net 1.1 framework and ... I'm trying to update an existing device XPe SP1, Net framework 1.1 to ... it says it can't perform the upgrade because the ...
    (microsoft.public.windowsxp.embedded)
  • Re: Figuring out which version of .NET an assembly is dependent on
    ... You have installed framework 3.5 SP1. ... In your deployment project what ever framework you ... After installing SP1 of 3.5 it will replace various assemblies of ...
    (microsoft.public.vsnet.general)
  • Re: NetDataContract doesnt work on Windows XP Pro machine?!
    ... I'm going to try installing VS 2008 SP1 today to see if that solves the ... type I have marked with the NetDataContract attribute. ... XP machine has .NET Framework 3.0 installed. ...
    (microsoft.public.dotnet.languages.csharp)