Re: Relationship between versions of .Net Framework

On 18 Jun, 01:13, "Alvin Bruney [ASP.NET MVP]" <vapor dan using hot
male spam filter> wrote:
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.

That's not an issue, your application can only run one version of the .NET
framework at execution time. Further, all versions of the framework are side
by side compatible.

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?

Yes, but not for the reasons you think. 3.5 SP1 actually installs all
service packs for 2.0 and 3.0. The 3.5 SP1 memory leak bug fix, if it exists
at all, would most likely be retrofitted in a service pack for earlier
frameworks. Don't install 3.5 SP1 if you haven't tested the previous SPs for
earlier frameworks. As Jon suggested, VPC is the best way to go.

I'll take a peak at the complete of bug fixes in 3.5 SP1 to see if any deal
with imaging memory leaks. If I find, I'll update this post. Otherwise,
assume I didn't find any.

--

Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The O.W.C. Black Book, 2nd Edition
Exclusively onwww.lulu.com/owc$19.99
-------------------------------------------------------

"P Chase" <peter.ch...@xxxxxxxxxxxxxxxxxx> wrote in message

news:a8568cac-8684-4f64-93d2-3b410d0135da@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

On 17 Jun, 13:00, "Alvin Bruney [ASP.NET MVP]" <vapor dan using hot
male spam filter> wrote:
what memory leak are you seeing? You need to describe it better and give
some more details.

--

Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The O.W.C. Black Book, 2nd Edition
Exclusively onwww.lulu.com/owc$19.99
-------------------------------------------------------

"P Chase" <peter.ch...@xxxxxxxxxxxxxxxxxx> wrote in message

news:9f5a9847-26a7-4c2d-802e-a4b826b619f7@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

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).

My question was not intended to be about the specific issue I am
facing, but the general issue of whether patching .Net Framework 3.5
would also affect my code which is a client of .Net Framework 3.0. I
don't understand how the various versions of .Net that have been
installed interact.

However, since you ask, I can also give details of the specific issue
I am trying to resolve.

I have a server application that uses FlowDocument to turn some text
and images into a nice-looking document. The FlowDocument is
constructed from XAML.

If the FlowDocument has no images in it, then when I am finished with
it, all memory is happily released. But if there are Image elements in
the XAML, then lots of memory is leaked, and the files providing the
image contents are held open.

I read that some image-related leaks in .Net Framework itself are
fixed by 3.5 SP1. So I want to know whether these might fix my issues.
I hoped to get an indication of the likelihood of this, before going
to the trouble of installing SP1, particularly if it might be
difficult to uninstall.

http://blogs.msdn.com/jgoldb/archive/2008/05/04/memory-leaks-in-wpf-b...



In the end, I was brave/foolish and just tried 3.5 SP1 on my main PC.
Nothing bad happened, but neither did the leak go away. So I guess
Microsoft aren't going to sort out this problem for me. I deinstalled
3.5 SP1 afterwards, and happily all still seems to be working.

Does anyone have any alternative ideas how I might be able to
persuade .Net to release the Images that it created, when parsing the
XAML text for my FlowDocument?
.

Relevant Pages

  • Re: Microsoft .Net Framework
    ... I distinctly recall installing Microsoft. ... Microsoft .Net Framework 1.1 ... Microsoft .Net Framework 2.0 Service Pack 2 ...
    (microsoft.public.windowsxp.newusers)
  • 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)
  • Setupu fails
    ... Installing dotnet framework gives errors. ... This is the error file. ... Error Code: 0x80070643 ...
    (microsoft.public.sqlserver.setup)
  • 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: Booting up XPPro
    ... framework service pack 1 1.14322.2032 which restored automatic logon. ... After installing HP Printer Software on my XPPro Computer I ... Microsoft's .NET framework 1.1 be installed as well. ... Enter the name of your user account in the User Name box. ...
    (microsoft.public.windowsxp.configuration_manage)