The Top 5 WPF and Silverlight Gotchas

8 Kicks

submitted by Red Gate 9 months, 12 days ago

As WPF and Silverlight sit on the .NET framework, they’re subject to the rules of the Garbage Collector. That means there are a few unique ways in which WPF will cause your application to leak memory, and Chris Farrell points out the most prominent culprits.

2 comments |category: Windows Presentation Foundation |Views: 200
Tweet

tags: WPF another

Everyones tags:

Your Tags:

Please login or signup.

Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

"Kick It" text
"Kick It" background
kick count text
kick count background
border

Simply copy and paste this HTML into your blog post.

Users who kicked this story:

kingbee71(511) -

vivekamar(6106) -

SuprotimAgarwal(715) -

happer(145)

More who kicked this story...

Comments:

posted by vijayst(1311) 9 months, 12 days ago 0

Garbage collection is one of the least understood concepts within the .Net framework. This article shows why. I did not realize that failure to clear a two-way binding can cause a leak. A very well written article.

posted by bsenoff(1583) 8 months, 13 days ago 0

Best of DNK for August 2011!

Most Active Users

What's this?