Great information on how to create background workers. I took the approach of writing a subclass since it was a longer running process.
There are lots of great free tools out there to help you profile and find memory leaks in your C# WPF application. My favorite for finding memory leaks has recently been CLR Profiler. I also found the SlimTune to be helpful as well. Enjoy the links!
- Using CLR Profiler - http://blogs.msdn.com/jgoldb/archive/2008/02/04/finding-memory-leaks-in-wpf-based-applications.aspx
- SlimTune - http://code.google.com/p/slimtune/
- If you have visual studio 2008 you can still get the profiling piece - http://codeka.com/blogs/index.php/2009/03/21/got-visual-studio-2008-professional-want
- Using visual studio profiling - http://msdn.microsoft.com/en-us/magazine/cc337887.aspx#S1
- Walkthrough - http://msdn.microsoft.com/en-us/library/ms182398(v=VS.90).aspx
- How to use the dump - http://support.microsoft.com/kb/315271
- Attaching profiler - http://msdn.microsoft.com/en-us/library/dd255435.aspx
- Download for debugging tools 64 bit version - http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx#