-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
Explicitly Enumerate the Subset of C# Blazor WASM Supports #42850
Comments
@devshgraphicsprogramming thanks for contacting us. Can you point out to the article that you are referring to? (For future reference, if you are on a doc page, you can provide feedback about the page directly there). The only language feature that I can think of will have issues is |
Hi @devshgraphicsprogramming. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time. |
I don't see a list or a link to an explainer about what isnt available. |
@devshgraphicsprogramming thanks for the additional details. There is no static list that you can look anywhere for that. The framework APIs are annotated for the most part when they are specific to a given platform with the |
This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes. See our Issue Management Policies for more information. |
Summary
The Blazor documentation says that some things may throw exceptions or fail to run/compile if deployed as Blazor WASM, yet the MSDN documentation never states what these features are exactly!
The text was updated successfully, but these errors were encountered: