Provide a way to disable the NotSupportedException diagnostics we provide for bindings without the attribute - #2325
Merged
manodasanW merged 2 commits intoMar 11, 2026
Conversation
…ableCustomProperty
Sergio0694
approved these changes
Mar 11, 2026
manodasanW
deleted the
manodasanw/bindableCustomPropertyDiagnosticsSuppress
branch
March 11, 2026 20:21
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We are seeing scenarios where AOT compiled components being loaded in other existing native apps can run into issues where existing failing bindings in those apps can end up triggering our NotSupportException that we throw for purposes of diagnostics and catching issues with respect to C# binding scenarios. Given we also now have XamlCompiler diagnostics too, providing an option for disabling the NotSupportedException we throw if someone runs into this edge case.