Obsolete Frame for NET9 in favor of Border #23184
Merged
Conversation
This file contains 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
pictos
reviewed
Jun 24, 2024
PureWeen
force-pushed
the
deprecate_frame
branch
from
97e200e
to
11bd8ea
Compare
jfversluis
reviewed
Jun 28, 2024
src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue15330.cs
Outdated
Show resolved
Hide resolved
jfversluis
previously approved these changes
Jun 28, 2024
|
Device test failures are unrelated and will be fixed by |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
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.
Description of Change
We're at the point with
Borderwhere we're seeing the majority ofFrameissues users are having being resolved by usingBorder. For .NET9 we're going to markFrameas obsolete so that we can fully removeFramein .NET 10TODO
Add documentation for migrating from Frame to Border