Question

When is the “Path=” xaml syntax required when specifying a binding to a property?
I see this “Path=” pretty much exclusively when there is a nested property binding (ex: Path=Person.FirstName).

Thanks!

Answer 1

Think of it like initializing a class in C#. If the “Binding” class has a constructor that takes a path, you could do this:

new Binding("Person.FirstName");

… or this:

new Binding { Path = "Person.FirstName" };

The two are the same, for all intents and purposes. XAML is doing the same thing. If you omit the “Path=” you’re passing a path into the constructor for Binding, but if you include it you’re setting the value after the fact.

I often leave the “Path=” out, especially if I’m declaring a binding with no other properties set, like {Binding FirstName}.