Book Image

MCTS: Microsoft Silverlight 4 Development (70-506) Certification Guide

By : Johnny Tordgeman
Book Image

MCTS: Microsoft Silverlight 4 Development (70-506) Certification Guide

By: Johnny Tordgeman

Overview of this book

Microsoft Silverlight is a powerful development platform for creating engaging, interactive applications for many screens across the Web, desktop, and mobile devices. Silverlight is also a great (and growing) Line-Of-Business platform and is increasingly being used to build data-driven business applications. Silverlight is based on familiar .NET languages such as C# which enables existing .NET developers to get started developing rich internet applications almost immediately. "MCTS: Microsoft Silverlight 4 Development (70-506) Certification Guide" will show you how to prepare for and pass the (70-506): TS: Microsoft Silverlight 4 Development exam.Packed with practical examples and Q&As, MCTS: Microsoft Silverlight 4 Development (70-506) Certification Guide starts by showing you how to lay out a user interface, enhance the user interface, implement application logic, work with data and interact with a host platform amongst others.
Table of Contents (15 chapters)
MCTS: Microsoft Silverlight 4 Development (70-506) Certification Guide
About the Author
About the Reviewers

Working with dependency properties

If I had to sum up the dependency properties in a single term, I would say that dependency properties are the regular property systems on steroids. The dependency properties really take what you know about properties to a whole new level, but that is also why it is one of the hardest concepts in Silverlight to grasp.

Most properties used on the UI objects in Silverlight use dependency properties. The most common place to write your own dependency properties is when writing your own control. The dependency properties are necessary when you wish to use data binding or styling, so if you think back about the projects we created in this book so far, you've used quite a lot of dependency properties but didn't even know that. Every time you bind a property in XAML, you're actually using a dependency property.

To make my point clearer, let's assume that you are writing a custom control. Other than the regular properties you get from inheriting from control, you...