Re: Relationship between versions of .Net Framework

Tech-Archive recommends: Fix windows errors by optimizing your registry

On 17 Jun, 13:52, Rory Becker <rorybec...@xxxxxxxxxxxxxxxx> wrote:
Hello P,

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 would also check to see if your issues are not already cleared up by .Net
3.0 SP1

This would have been installed (I think) by an installation of .Net 3.5 (
If you have that present on your machine) however it is available fromhttp://www.microsoft.com/downloads/details.aspx?familyid=EC2CA85D-B25...

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.

Typically an application attempts to "use" the version of the framework that
it was compiled against. If this is not available I believe it will use the
latest available verion. this only applies to 1.0, 1.1 and 2.0 however. 3.0
and 3.5 use the 2.0 verion of the CLR and so may be considered to be additions
to the 2.0 libraries. This is much the same as if you had included third
party libraries in your app

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?

Hard to say. I would have expected such things fixed in say 3.0 SP2 which
may itself be included in 3.5 SP1.

But this is Microsoft, and with the best will in the world, general consensus
(although not unanimous) is that they have issues with their versioning within
.Net. Nothing wrong as such, just a touch difficult to follow sometimes :)

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

Do yourself a favour and don't "Try" anything on a machine you are not prepared
to have die on you. I'm not trying to suggest that this will happen, but
I've found it really pays to be careful with anything beta

I'm really not sure how helpful any of this will be to you but hopefully
something will be :)

--
Rory

Thanks for your help.

I already have the latest non-beta Service Packs of everything. So I
think that the beta of 3.5 SP1 is my only hope for an instant fix. But
not sure if I dare try it, particularly as I don't really know whether
the leaks fixed in 3.5 SP1 are the ones I'm experiencing.
.

Relevant Pages

  • Re: Relationship between versions of .Net Framework
    ... I am falling foul of some memory leaks in the framework, ... Microsoft claim to have fixed in .Net Framework 3.5 SP1. ... I would have expected such things fixed in say 3.0 SP2 which may itself be included in 3.5 SP1. ...
    (microsoft.public.dotnet.framework)
  • Sinking events in IE script - Problem with .net 1.1 sp1
    ... I have de-installed SP1 and can confirm that the problem is ... solved by reverting to the original 1.1 framework. ... I have created a simple control with an event. ... SecurityPermissionFlag.UnmanagedCode is asserted before firing the event, ...
    (microsoft.public.dotnet.framework.windowsforms)
  • 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)
  • 2.0 versus 2.0 SP1 -> =?ISO-8859-15?Q?gr=F6=DFeres_Problem?=
    ... Somit installiert das Setup gegebenenfalls das Framework 2.0 OHNE SP1. ... VS2008 scheint dem entgegen wirken zu wollen, in dem es einige Kern-DLLs mit in das Programmverzeichnis wirft Die Anwendung wiederum weigert sich auf Zielrechnern allerdings, die im lokalen Ordner liegende System.dll zu nutzen und beharrt weiterhin auf jene aus der GAC ...
    (microsoft.public.de.german.entwickler.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)