[Blazor WebAssembly] Change web app manifest extension to “webmanifest”

[christianliebel]

[Blazor WebAssembly] Change web app manifest extension to “webmanifest”

• You've read the Contributor Guide and Code of Conduct.
• You've included unit or integration tests for your change, where applicable.
• You've included inline docs for your change, where applicable.
• There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.

Changes web app manifest extension from "json" to "webmanifest"

Description

Changes the extension of the web application manifest included by the Blazor WebAssembly project templates from "json" to "webmanifest", the official file extension. This helps servers to deliver the file with the official media type (application/manifest+json).

Fixes #43755

[ghost]

Thanks for your PR, @christianliebel. Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

[dnfadmin]

All CLA requirements met.

[javiercn]

Looks like the tests likely need to be updated and the docs might also need to be updated.

We should ping guardrex about the docs after this is merged.

[christianliebel]

@javiercn I have updated the tests. A Blazor Server test still fails because dotnet publish does not work. But this should have nothing to do with my changes. Could you look into this for me?

Let me know if you need any help with the docs.

[TanayParikh]

Hey @christianliebel, thanks for the PR. We're ready to take this in now. Could you please resolve the merge conflict, and I'll look into any CI flakiness if required.

[christianliebel]

@TanayParikh Done!

[TanayParikh]

/azp run aspnetcore-quarantined-pr

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[TanayParikh]

[TanayParikh]

Thanks @christianliebel!

I think thats all the webmanifest PRs. Please let me know if I missed any!

[christianliebel]

@TanayParikh Looks good, thanks!!

[ghost]

Hi @christianliebel. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context.