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

Managing the visual state

Visual states define how a control looks in certain situations. Try to think about the default Silverlight Button control. Whenever you hover over it, it changes color. This change is an example of state, hover state in that case. The default look of a control represents its normal state. But in most cases, your control will have more than a single state. To help you manage these states, Silverlight provides you with the VisualStateManager element. This element manages the states and the transition between them. A state doesn't have to be a change of color. It can be used to change an object size, border or even to transform it using one of the transformations we discussed earlier.

Each state is identified by its Name and GroupName properties. GroupName defines the group of which the state belongs to. A question that often rises up at this point is why do I need to group states? Can't I just create a big group of states and put them all in there? The answer is ...