Oh dam it, I was using 6.0.6. I upgraded and every thing works like a dream
except on particular thing, that I think is a bug!
Let us call Navigation Property 'NP' in the description below.
If you have an entity 'a' that has a NP 'b' where 'b' has another NP 'c'. Then you want to bind to for example
a.b.c.name in XAML somthing like:
Text="{Binding b.c.name, Mode=OneWay}"
where the the parent control has data context bound such:
DataContext="{Binding a, Mode=TwoWay}"
This works fine as long as 'b' is not a NullEntity. Unfortunately in my case b is nullable and therefore in that case the bound text box shold display empty. What happens however is that Visual Studio Just In Time Debugger pops up with this message:
An unhandled exception ('Unhandled Error in Silverlihgt Applicatoin Code: 4004
Categorey: ManagerdRuntimeError
Message: System.InvalidOperationException: Collection was modified;
enumeration operation may not execute.
Entering the debuger (if run without debugging) requests "eval code".
This is quite well known error indicating that a collection is modified in a foreach loop or similar.
I have uploaded screenshot from the debugger, as well as table structure I'm deailing with in the database when this happens if that helps:
uploads/508/NaviagationBug.zip