Skip to content

Conversation

@jonathanpeppers
Copy link
Member

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.

  • Documentation around building xamarin-android
  • Error/warning messages

I also updated a few things other things that should say .NET 6:

  • NuGet.config sources in MSBuild tests
  • @(FrameworkListRootAttributes) for our .NET 6 packages

I did not update various code comments, as most of them say .NET 5+
and are not user-facing.

Other changes in OneDotNet.md:

  • Started a new Runtime behavior section with a link to
    String.IndexOf() behavior.
  • Link to net6-samples as the source for .NET 6 example projects and
    installation instructions.

@jonathanpeppers
Copy link
Member Author

I think the Desugar test failures will be fixed by: #5305

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.

* Documentation around building `xamarin-android`
* Error/warning messages

I also updated a few things other things that should say .NET 6:

* `NuGet.config` sources in MSBuild tests
* `@(FrameworkListRootAttributes)` for our .NET 6 packages

I did not update various code comments, as most of them say .NET 5+
and are not user-facing.

Other changes in `OneDotNet.md`:

* Started a new `Runtime behavior` section with a link to
  `String.IndexOf()` behavior.
* Link to `net6-samples` as the source for .NET 6 example projects and
  installation instructions.
@jonpryor jonpryor merged commit 55faee0 into dotnet:master Nov 19, 2020
@jonathanpeppers jonathanpeppers deleted the net6.0-docs branch November 19, 2020 01:12
@github-actions github-actions bot locked and limited conversation to collaborators Jan 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants