No other cache/registry stores XAML data apart from UI resources.

If you revert the NsProp name back to "Id" and the binding path in the xaml, does the TextBlock show the text again?

Yes - if I change it back it works..

Note that this way you are rebuilding the entire data base each time. As you increase the number of xamls this can be quite inefficient. A simple "build" command is able to detect changes and start and incremental build.

Thanks for the tip, I'll change it to use the build command..

Yes - if I change it back it works..

Ok, so let's do it step by step to figure out what is happening.

1) Set the property name in code as "Desc", and leave it as "Id" in the xaml. Compile your application, build the resources and see if text is shown.

2) Set the property name in code as "Id", and modify the xaml to "Desc". Compile your application, build the resources and see if text is shown.

1) Set the property name in code as "Desc", and leave it as "Id" in the xaml. Compile your application, build the resources and see if text is shown.

Didn't work..

2) Set the property name in code as "Id", and modify the xaml to "Desc". Compile your application, build the resources and see if text is shown.

Didn't work..

I also tried using third new name for that property, but it seems that the TextBlock has some special attachment to the "Id" name It won't let it go..

Could you please create a ticket in the bugtracker (bugs.noesisengine.com) and attach the xaml and the code that is failing, so I can take a look and try to reproduce the error?

I just opened a new issue on the bug tracker with code and XAML file to reproduce this issue.

Hi,

I can confirm that Data Binding Issue fixed on the 1.1.3 version.

Thanks !