Re: Relationship between versions of .Net Framework
- From: P Chase <peter.chase@xxxxxxxxxxxxxxxxxx>
- Date: Tue, 17 Jun 2008 05:18:38 -0700 (PDT)
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-based-applications-blog-update.aspx
.
- Follow-Ups:
- Re: Relationship between versions of .Net Framework
- From: Alvin Bruney [ASP.NET MVP]
- Re: Relationship between versions of .Net Framework
- References:
- Relationship between versions of .Net Framework
- From: P Chase
- Re: Relationship between versions of .Net Framework
- From: Alvin Bruney [ASP.NET MVP]
- Relationship between versions of .Net Framework
- Prev by Date: Re: Relationship between versions of .Net Framework
- Next by Date: Re: Relationship between versions of .Net Framework
- Previous by thread: Re: Relationship between versions of .Net Framework
- Next by thread: Re: Relationship between versions of .Net Framework
- Index(es):
Relevant Pages
|