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
cannot enable "Support pages and views" for WebAssembly client projects #32453
Labels
aspnet-core/svc
blazor/subsvc
Blazor
doc-bug
Pri0
Urgent priority
Source - Docs.ms
Docs Customer feedback via GitHub Issue
Comments
dotnet-bot
added
⌚ Not Triaged
aspnet-core/svc
blazor/subsvc
Source - Docs.ms
Docs Customer feedback via GitHub Issue
labels
Apr 28, 2024
😎 Welcome April! Summertime is almost here! 🌞A green dinosaur 🦖 will be along shortly to assist. Stand-by ........ |
Thanks @ghhv! ... I'll get a PR up shortly to address this. |
There is content here to cover it, but the 🧀 has apparently moved over the years (OR ... I had this written against Blazor Server in a pivot that was merged with Blazor WASM coverage). Either way, the text was trying to cover it here in the ... ... section. I'll update that guidance. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
aspnet-core/svc
blazor/subsvc
Blazor
doc-bug
Pri0
Urgent priority
Source - Docs.ms
Docs Customer feedback via GitHub Issue
Description
[Enter feedback here]
You should highlight that you cannot enable "Support pages and views" for WebAssembly client projects. If you do, you get the painful error, "no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier 'browser-wasm'"
I highlighted the changes made and a fix here - dotnet/aspnetcore#53671 (comment)
Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/components/class-libraries?view=aspnetcore-8.0&tabs=visual-studio
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/components/class-libraries.md
Document ID
a92c88d3-6ee8-1e69-f4c3-49eb82909746
Article author
@guardrex
The text was updated successfully, but these errors were encountered: