* [X] chain debug ctors
* unit test for 7097
* [X] Reuse baseclass namescope if it exists
If a xaml control derives from another xaml control, thy both should share the same
NameScope. This add a check if the xaml root already has a NameScope (set by the base)
and reuses it.
This fixes 2 regressions introduced by #7040 and some other unreported edge cases.
- fixes#7097
- fixes#7286
* avoid repeting linq queries
if the object creation already creates a namescope (because it's created from xaml), do not override the namescope
- fixes#6192
- fixes #AB957727
- fixes#6902
* [Xaml] un-obsolete XamlLoader.Create
now that we plan to load Xaml files without compiling the ctor, keeping
XamlLoader.Create makes sense.
* [Xaml] add FallbackTypeResolver
* Additional tests
* More tests
* Further tests
* [Xaml] provide an mock App
* [C] allow re-registering implicit styles
* Some tweaks and reinstated test with missing resource key
* Add StyleAppliedToDerivedTypesAppliesToDerivedUnknownType test
* Renamed some stuff for consistency. Added some CSS tests.
* Remove use of ValueTuple
* Temporarily disable failing tests
* redirect valueprovider exceptions to the handler, allow the handler to intercept excpetion with Create()
* fix the CSS situation
* new callback, works for CSS
As part of #2556, the namescoping tree was assumed to be equiv to the
object tree, which is obviously wrong. This fixes it, while keeping the
old behavior as a fallback.
We might go further, but I can't come up with a reasonable scenario
failing.
- fixes#3821
* [Xaml] open non-generic FindByName()
* [Xaml[C]] Only set the namescope when it's different
avoid setting the NamesCope if it's the same as the parent.
Also provide an IReferenceProvider for markup extension that need to
replicate the x:Reference behavior.
* [All] Normalize Obsolete attributes.
Make sure we include the version in which the member was deprecated and
consistent instructions for working around the deprecation, if
applicable.
* Update docs