[One .NET] update user-facing messages from .NET 5 to .NET 6 #5300
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.
Since 6f761ea gets us on a build of .NET 6, we can update all
user-facing messaging to say .NET 6 instead of .NET 5.
xamarin-androidI also updated a few things other things that should say .NET 6:
NuGet.configsources in MSBuild tests@(FrameworkListRootAttributes)for our .NET 6 packagesI did not update various code comments, as most of them say .NET 5+
and are not user-facing.
Other changes in
OneDotNet.md:Runtime behaviorsection with a link toString.IndexOf()behavior.net6-samplesas the source for .NET 6 example projects andinstallation instructions.