Install
$ agentstack add skill-davidortinau-maui-skills-maui-data-binding ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
.NET MAUI Data Binding
Don't specify redundant binding modes
Set Mode explicitly only when overriding the default. Most properties already have the right default:
Compiled bindings — x:DataType placement rules
Compiled bindings are 8–20× faster than reflection-based bindings. Enable with x:DataType.
Place x:DataType only where BindingContext is set:
- Page root — where you assign
BindingContext. - DataTemplate — which creates a new binding scope.
Do not scatter x:DataType on child elements. Adding x:DataType="x:Object" on children to "escape" compiled bindings is an anti-pattern — it disables compile-time checking and reintroduces reflection. To opt out for a single binding, use x:DataType="{x:Null}" on that element (see also: maui-xaml-authoring skill).
DataTemplate always needs its own x:DataType:
Treat compiler warnings as errors in CI
| Warning | Meaning | |---------|---------| | XC0022 | Binding path not found on the declared x:DataType | | XC0023 | Property is not bindable | | XC0024 | x:DataType type not found | | XC0025 | Binding used without x:DataType (non-compiled fallback) |
XC0022;XC0025
.NET 9+ compiled code bindings
Fully AOT-safe, no reflection:
label.SetBinding(Label.TextProperty,
static (PersonViewModel vm) => vm.FullName);
entry.SetBinding(Entry.TextProperty,
static (PersonViewModel vm) => vm.Age,
mode: BindingMode.TwoWay,
converter: new IntToStringConverter());
Threading caveat
MAUI automatically marshals PropertyChanged to the UI thread — you can raise it from any thread. However, direct ObservableCollection mutations (Add/Remove) from background threads may still crash:
// ✅ Safe for PropertyChanged
await Task.Run(() => Items = LoadData());
// ⚠️ ObservableCollection.Add — dispatch to UI thread
MainThread.BeginInvokeOnMainThread(() => Items.Add(newItem));
Performance tips
- Compiled bindings eliminate reflection — always prefer them.
- NativeAOT / trimming: Reflection-based bindings break under trimming. Compiled bindings (XAML
x:DataTypeor codeSetBindingwith lambdas) are trimmer- and AOT-safe. - Use
OneTimemode for truly static data to skip change-tracking registration. - Avoid complex converter chains in hot paths — pre-compute values in the ViewModel instead.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: davidortinau
- Source: davidortinau/maui-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.