Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Xamarin - update references - AspNetCore.Docs - Blazor docs only #34325

Closed
wadepickett opened this issue Dec 10, 2024 · 3 comments · Fixed by #34328
Closed

Xamarin - update references - AspNetCore.Docs - Blazor docs only #34325

wadepickett opened this issue Dec 10, 2024 · 3 comments · Fixed by #34328
Assignees
Labels

Comments

@wadepickett
Copy link
Contributor

wadepickett commented Dec 10, 2024

Xamarin should no longer be referred to and we should refer to or direct to Maui instead:
https://learn.microsoft.com/en-us/dotnet/maui/what-is-maui?view=net-maui-9.0

In the AspNetCore.Docs repo, for Blazor content only

  • Remove all references to "Xamarin" or update to ".NET Multi-platform App UI (.NET MAUI)" for first reference and ".NET MAUI" for following references in the same doc.
  • If a topic centers on .NET MAUI and requires a complete rewrite rather than just an updated link or reference update, and/or requires a code sample update, AND we decide not to retire or archive it as the solution, then identify it here and create a new tracking issue for that work.

Currently there are around 14 files referencing "Xamarin", in this repo, a few of those are for Blazor docs and the rest for non-Blazor docs.

See also #34324 for non-blazor effort.

@wadepickett wadepickett added the doc-out-of-date Doc is out of date with the current version label Dec 10, 2024
@wadepickett
Copy link
Contributor Author

@guardrex, I figured you would want to handle the few Blazor docs that still reference Xamarin for this update effort, so I created this separate Blazor related issue. If you don't want to handle it, feel free to assign it to me.

@guardrex
Copy link
Collaborator

Thx @wadepickett ... I'll take care of it very soon, probably tomorrow morning.

@wadepickett
Copy link
Contributor Author

Great! I don't think this has to be done right away. January sprint for example would be fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants