Binding Context
In DotVVM, each HTML element or DotVVM control has the DataContext
property. Using this property, you can change the context in which data bindings are evaluated.
Let's have the following view and viewmodel:
@viewModel AddressViewModel, DotvvmDemo
<div DataContext="{value: Customer}">
{{value: Name}}
</div>
public class AddressViewModel {
public Customer Customer { get; set; }
}
public class Customer {
public string Name { get; set; }
}
The DataContext
property will make all bindings on the <div>
element and all bindings inside this element to be evaluated in the context of the
Customer
property of the viewmodel.
If the DataContext
binding is not present, the binding inside the <div>
would have to be {{value: Customer.Name}}
.
Null DataContext
There is also one helpful feature. If the DataContext
of any element is null
, the element is removed from the DOM and the bindings inside this element
are not evaluated at all.
When you set some value in the DataContext
property, the element re-appears in the DOM.
If you don't want the <div>
element to hide, the DataContext
property must point to some property which is not null
.
Binding Context Variables
Inside elements that change the DataContext
property, you can use the following binding context variables to navigate the viewmodel hierarchy.
_root
accesses the top-level viewmodel (the viewmodel of the page)._parent
accesses the parent binding context._parent2
accesses the parent's parent binding context and so on..._this
references the current context. It is useful when you need to pass the currentDataContext
e.g. as an argument to a method.
For example, the following binding calls the DeleteAddress
method in the page viewmodel and passes the current binding context as an argument.
<div DataContext="{value: Company}">
<dot:Button Click="{command: _root.DeleteAddress(_this)}" />
</div>