Fix typo: keep private field as UInt16 in CLS compliance #50799
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.
Summary
Fixed the code in the CLS compliance documentation where the private field was incorrectly changed to
Int16.The documentation states:
However, the code example in
public2.csshowed both the private and public members changed toInt16, which contradicts the documentation.Fix
Changed
private Int16 personAgeback toprivate UInt16 personAge.Fixes issue: #49691