One of the weaknesses in XAML and Silverlight is when you are doing data binding, where you refer to a bound property by the property name in the XAML. If you do a typo in the XAML or change the property name in the C# code forgetting to update it in the XAML code you get no binding.

Is there any method of avoiding this for example by static resources?

A related question is regarding the OnPropertyChanged event. Example below where overriding that event handler in an Entity class:

        protected override void OnPropertyChanged(System.ComponentModel.PropertyChangedEventArgs e)

        {

            base.OnPropertyChanged(e);

            if(e.PropertyName == "p_tsID" || e.PropertyName == "p_ts")

            {

// Do some stuff

            }

        }

In the above example can I somehow get the property names by code instead of using hard-coded strings ("p_tsID", "p_ts")? That would eliminate the risk if I later decide to change the name of those properties in the entity model and forget to update those strings accordingly.
You have this possibility in the EntitySet's via the EntitySetName property. But I can't find how to access that for Entity-Properties.

EntItem.EntityPropertyNames.p_tsID  returns "p_tsID" and so on.

The first question is still open.

Hi tj62;

There are several options that I know of to minimize the error of binding with a property that doesn't exist:

System.Windows.Data Error: BindingExpression path error: 'Outputxxxxx' property not found on 'SilverlightApplication1.MainPageViewModel' 'SilverlightApplication1.MainPageViewModel' (HashCode=53180767). BindingExpression: Path='Outputxxxxx' DataItem='SilverlightApplication1.MainPageViewModel' (HashCode=53180767); target element is 'System.Windows.Controls.TextBox' (Name='txtOutput'); target property is 'Text' (type 'System.String')..

2. You can use a Fallback value markup as a default value in case a binding error occurs.

3. By googling this, I was able to find other options that other developers seem to use. One of them that I think is more helpful than the rest is this.

http://karlshifflett.wordpress.com/2009/06/08/glimpse-for-silverlight-viewing-exceptions-and-binding-errors/ - http://karlshifflett.wordpress.com/2009/06/08/glimpse-for-silverlight-viewing-exceptions-and-binding-errors/

Hope this helps.