Add proper handling when a property’s backing field cannot be inferred or the unsafe accessor cannot be generated.#36720
Open
kawasaniac wants to merge 2 commits intodotnet:mainfrom
Open
Add proper handling when a property’s backing field cannot be inferred or the unsafe accessor cannot be generated.#36720kawasaniac wants to merge 2 commits intodotnet:mainfrom
kawasaniac wants to merge 2 commits intodotnet:mainfrom
Conversation
- Add proper handling when a property’s backing field cannot be inferred or the unsafe accessor cannot be generated. - Add DesignStrings methods and entries to .resx Fixes dotnet#35219
Author
|
@dotnet-policy-service agree |
AndriySvyryd
requested changes
Sep 11, 2025
Co-authored-by: Andriy Svyryd <AndriySvyryd@users.noreply.github.com>
roji
force-pushed
the
main
branch
2 times, most recently
from
249ae47 to
6b86657
Compare
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
2 participants
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.
My take on adding additional handling for the following issue: #35219
Throws InvalidOperationException with proper message as in DesignStrings (CompiledModelBackingFieldNotFound and CompiledModelUnsafeAccessorNull). Plus added additional exceptions specifically for this case.