Add WPF breaking change documentation for MC3063 error with empty Grid definitions #47923
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.
This PR adds documentation for a WPF breaking change introduced in .NET 10 Preview 5 where empty
<Grid.ColumnDefinitions>or<Grid.RowDefinitions>declarations now cause MC3063 compilation errors.Changes Made
docs/core/compatibility/wpf/10.0/empty-grid-definitions.md- Complete breaking change documentation with examples and migration guidancedocs/core/compatibility/10.0.md- Added entry to the WPF sectiondocs/core/compatibility/toc.yml- Added navigation entry for the new breaking changeBreaking Change Details
Previously, WPF applications could compile successfully with empty Grid definitions like this:
Starting with .NET 10 Preview 5, this now fails with:
The documentation provides two clear migration paths:
<ColumnDefinition />or<RowDefinition />elementsThis change is a consequence of implementing Grid XAML Shorthand Syntax support, which requires stricter parsing of property declarations.
Fixes #47743.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.
Internal previews