This project is to help us to resolve all the memory issues we are having with our WPF Application. Basically we have a messaging client that starts up with an initial payload of 70,000k - 100,000k memory and keeps increasing as we do tasks. We are using a skin engine which allows us to design our own custom windows form. - startup (70,000k - 100,000k) - login (goes to 150,000k) - send a message (goes to 170,000k) - start a group session (goes to 750,000k) - send a ppt which is converted to images (goes to 1000,000k) - share a screen (goes to 1100000k) - stores bitmaps of the screen capture - observe screens (goes to 1217,000k) - stores a bunch of bitmaps whcih are not disposed Notice that the memory never goes down even when we close the form. Our app uses a lot of bindings and we need someone who is familiar with all the issues related to memory management in a MVVM paradigm. We need someone who is familiar with all the binding management with Xaml and code as we think that the binding are not beeing disposed. We are also using MVVM, and we notice that when we show a view, the view is binded multiple times, but the bidnings are not disposed. We need someone to review these and propose the changes and verify that the memory issues has been resolved. Our code build is pretty huge and we are probably looking at close to 60 xaml files that needs to be modified - but once the logic is correct, these should be easily done. Secondly - we need someone who knows how to use the profiling tool in visual studio to detect and fix these leaks. We will need the vendor to provide us proof using the memory profiler that the results has been achieved. - /en-us/library/aa969767.aspx Bidders should be familiar with these concepts - /kb/938416 - /2011/10/top-3-memory-leak-inducing-pitfalls-of-wpf-programming/ - /b/jgoldb/archive/2008/02/04/finding-memory-leaks-in-wpf-based-applications.aspx Thirdly, we would like to implement a garbage collection subroutine that will run on the idle process so that memory can be reclaimed once the above fixes has been done. GC will not reclaim the memory if the above fixes are not done. Lastly, the person should help propose what can and cannot be done and why and how to mitigate these issues. . Note all the functionality of the program must be retained. Desired Skills: .NET C# Windows Presentation Foundation (WPF) Keywords: Software Application