(X) Hide this SilverlightShow next training events: Getting started with the Silverlight 5 Beta - a free 1 hour webinar on May 11th, by Michael Crump. Join at 10 am PST.
XNA for Windows Phone 7 - a 3 day training by MCC Peter Kuhn. June 1-3, 9 am - 1.30 pm PST. Sign up early-bird for $199.
Skip Navigation LinksHome / Search


Results Per Page

Found 28 results for Dependency Properties.
Date between: <not defined> and <not defined>
Search in: News , Articles , Tips , Shows , Showcase , Books

  • 1
  • 2
  • 3
Order by Publish Date   Ascending Title   Rating  

  • 0 comments  /  posted by  Gill Cleeren  on  Feb 01, 2011 (3 months ago)
    SilverlightShow and Gill Cleeren start a series of materials aimed at helping you get prepared for taking Microsoft Silverlight Exam 70-506. Through this series we will try to structure the resources available on the internet, grouping them by topic covered in the exam. Any feedback would be much appreciated! Thanks! 

    This article is Part 3 of the series on Microsoft Silverlight Exam:

    In the previous parts of this series on getting yourself ready for the Silverlight exam, we mainly looked at UI related items. In the very first part, we looked at how Silverlight could help with layout, navigation, media and the core controls. In part 2, we focused on the many features Silverlight has on board to create better user interfaces, such as the Visual State Manager, styling, templating and animations.

    This third part is going to be more aimed at the code-side of things. We’ll start our journey by looking at specifics of Silverlight such as routed events (these also exist in WPF by the way and asynchronous communication with services.

  • 0 comments  /  posted by  Silverlight Show  on  Jan 11, 2011 (3 months ago)

    SilverlightShow Page for all Silverlight and Windows Phone 7 (WP7) things on TwitterWith this blog post, Dan Wahlin tries to give some clarity around the concept of dependency properties in Silverlight.

    Source: Dan Wahlin's WebLog

    I have the opportunity to teach a lot of people about Silverlight (among other technologies) and one of the topics that definitely confuses people initially is the concept of dependency properties. I confess that when I first heard about them my initial thought was “Why do we need a specialized type of property?” While you can certainly use standard CLR properties in Silverlight applications, Silverlight relies heavily on dependency properties for just about everything it does behind the scenes. In fact, dependency properties are an essential part of the data binding, template, style and animation functionality available in Silverlight. They simply back standard CLR properties. In this post I wanted to put together a (hopefully) simple explanation of dependency properties and why you should care about them if you’re currently working with Silverlight or looking to move to it.
  • 0 comments  /  posted by  Silverlight Show  on  Jan 03, 2011 (4 months ago)

    Arik Poznanski discusses dependency property value resolution and gives an example to make it clearer.

    Source: Arik Poznanski's Blog

    One of the strength points for WPF is the ability to set a property value using a wide range of methods.

    Unfortunately, this variety makes it hard to understand how a WPF dependency property gets its final value. Hopefully this post will help organize this issue.

  • 0 comments  /  posted by  Silverlight Show  on  Dec 29, 2010 (4 months ago)

    In his previous post, Marlon Grech explained how Silverlight 4 lacks the UpdateSourceTrigger for PropertyChanged and how to overcome this issue for the TextBox. In this post he shows how to do this for any Dependency Property of any Framework element.

    Source: C# Disciples

    Please note that this post is quite an experimental one. Probably the use case you are looking for is for the textbox scenario, if that is the case I would suggest that you use the more explicit approach i.e the one I show in my previous post. The take away from this post should be more the idea of how things work rather than the actual code I am using here, this code was never tested in production thus it might contain memory leaks and other issues.

  • 0 comments  /  posted by  Beat Kiener  on  Aug 30, 2010 (8 months ago)
    The dependency property system is a pretty nice concept. Receiving notifications for dependency property changes on an existing object is a very common scenario in order to update the view model or the UI.

    This is quite easy in WPF. But Silverlight has a limited set of meta-data functionality around the dependency property system, because the DependencyPropertyDescriptor does exist in Silverlight. In order to get a workaround Beat Kiener found a solution in which he gets notified with help of the binding system.

    Source: Kiener's Blog

  • 0 comments  /  posted by  Silverlight Show  on  Aug 23, 2010 (8 months ago)
    In Part 3 of 4 of his series on styles in Silverlight, Gergely Orosz explores some further advanced topics like data binding, change notification, declaring styles in code behind and some other useful notes on styles.

    Source: ScottLogic

    This article is part 3 of 4 in a series covering everything that I think is worth knowing about styles in Silverlight. The previous parts of the series are Styles in Silverlight: an Introduction and Styles in Silverlight – Inheritance, Precedence and Other Advanced Topics.

  • Dependency Properties Made Easy

    0 comments  /  posted by  Silverlight Show  on  Jun 07, 2010 (11 months ago)
    Take a look at this short blog post about Dependency Properties written by David Kelley.

    Well the biggest issue is that if you want to animate properties of a custom control of some kind using data binding and what that change to filter into the UI of some control. Otherwise I try to avoid DP's as much as possible. 

  • Tip: For a truly read-only custom DependencyProperty in Silverlight, use a read-only CLR property instead

    0 comments  /  posted by  Silverlight Show  on  Apr 06, 2010 (more than a year ago)
    Here is David Anson's latest tip which comes as a response to comments on his previous post.

    My last tip outlined the best way I knew to approximate a WPF-like read-only DependencyProperty on Silverlight. (Aside: It's also a good way to implement coercion.) However, it suffers from the unavoidable problem that the actual DependencyProperty is still writable and can "twitch" if written to. The comments for that post proved to be very interesting - with two suggestions for alternate techniques.

  • Tip: The default value of a DependencyProperty is shared by all instances of the class that registers it

    0 comments  /  posted by  Silverlight Show  on  Mar 30, 2010 (more than a year ago)
    David Anson has another tip for you which again concerns DependencyProperty.

    The last two tips explained how to set the default value of a Silverlight/WPF DependencyProperty. But there's something you need to be aware of when you're using either technique: the default value of a DependencyProperty is shared by all instances of a class. This doesn't tend to matter for value types, immutable reference types, and sharable types (like brushes), but it affects mutable reference types and can lead to unexpected behavior.

  • Tip: Do not assign DependencyProperty values in a constructor; it prevents users from overriding them

    0 comments  /  posted by  Silverlight Show  on  Mar 26, 2010 (more than a year ago)
    Here is another tip of David Anson who offers you not to assign DependencyProperty values in a constructor.

    Initializing variables in an object's constructor is considered a Good Thing. Traditionally, initialization is done with a simple assignment that sets the variable to its initial value: MyProperty = 10;. However, doing that with a Silverlight/WPF DependencyProperty uses the CLR wrapper (more background here and here) and results in a call to SetValue that sets the local value of that property.

  • 1
  • 2
  • 3