WPF - Silverlight

< .NET < Development
TwitterFacebook
Get flash to fully experience Pearltrees
http://www.simple-talk.com/dotnet/performance/the-top-5-wpf-and-silverlight-gotchas/ 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. As I’m sure you know, WPF and Silverlight both use XAML as their interface markup language. The idea is that you can define your user interface (UI) and bind it to data without ever writing a line of code (healthy skepticism advised). Whether or not you buy into that vision, the UI possibilities can be stunning, and it seems Microsoft has created a technology that combines both power and flexibility. However, with that power comes responsibility.

The Top 5 WPF and Silverlight Gotchas

For more information on how to convert a silverligth theme (using VSM) to WPF: http://dotnet.org.za/rudi/archive/2008/10/29/silverlight-love-for-wpf.aspx

WPF Themes

http://wpfthemes.codeplex.com/

Caliburn: A Client Framework for WPF and Silverlight

http://caliburn.codeplex.com/ Copyright (c) 2008 Blue Spire Consulting, Inc. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.