3 ms·
I'm only familiar with XAML+WPF+C#+VS. One particular pet peeve of mine is the fact that it won't catch typos in data binding. If I have IsEnabled={Path IsEnab
by nwallin 7y ago
I'm only familiar with XAML+WPF+C#+VS.
One particular pet peeve of mine is the fact that it won't catch typos in data binding. If I have IsEnabled={Path IsEnabeld} in my XAML, the designer won't catch it. At runtime, the error is silently ignored. It just doesn't work, and no tooling, nothing other than triple checking every line of code will catch it.
Also it's really bad about picking up dependencies cross package, although it might be a problem in my org's config.
- bryanrasmussen 7y agook thanks, I was just thinking of elements and attribute names as being important.