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.

Sign up for GitHub

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

Jump to bottom

Don't build if used any of not supported API #38476

Closed
montyclt opened this issue Nov 29, 2018 · 4 comments
Closed

Don't build if used any of not supported API #38476

montyclt opened this issue Nov 29, 2018 · 4 comments
Labels
arch-wasm WebAssembly architecture area-Meta code-analyzer Marks an issue that suggests a Roslyn analyzer
Milestone
Future

Comments

@montyclt
Copy link

The Blazor FAQs says:

Yes, the .NET runtime used for Blazor supports .NET Standard 2.0. APIs that aren't supported in the browser throw Not Supported exceptions.

There are any list with unsopported APIs of the .NET Standard? Can a MSBuild task used to interrumpt the build and mark as error if any of this APIs are used instead of detect the error in execution time when the exception is thrown?
@montyclt montyclt changed the title Don't build is used any not supported API Don't build if used any of not supported API Nov 29, 2018
@danroth27
Copy link
Member

We don't have the precise list yet of the .NET Standard APIs that will work in Blazor. A lot of APIs already work today. Some APIs will work, but haven't been implemented yet. Others will never work because of the constraints of running in the browser. I can imagine us shipping an analyzer that provides a build time experience for detecting usage of APIs that won't work.

@aspnet-hello aspnet-hello transferred this issue from dotnet/blazor Dec 17, 2018
@pranavkm pranavkm transferred this issue from dotnet/aspnetcore Jun 26, 2020
@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added area-Meta untriaged New issue has not been triaged by the area owner labels Jun 26, 2020
@pranavkm pranavkm added arch-wasm WebAssembly architecture and removed area-Meta labels Jun 26, 2020
@pranavkm
Copy link
Contributor

/cc @lewing. Having the portability analyzer would help here.

@marek-safar marek-safar added code-analyzer Marks an issue that suggests a Roslyn analyzer and removed area-CoreLib-mono untriaged New issue has not been triaged by the area owner labels Jun 30, 2020
@marek-safar marek-safar added this to the Future milestone Jun 30, 2020
@marek-safar
Copy link
Contributor

This requires dotnet/designs#110 approval

@lewing
Copy link
Member

lewing commented Jun 10, 2022

Platform analyzers exist and are in use. closing

@lewing lewing closed this as completed Jun 10, 2022
Repository owner moved this from Future to Done in Triage POD for Reflection, META, etc. Jun 10, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Jul 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
arch-wasm WebAssembly architecture area-Meta code-analyzer Marks an issue that suggests a Roslyn analyzer
Projects
No open projects
Triage POD for Reflection, META, etc.
Status: Done
Milestone
Future
Development

No branches or pull requests
7 participants
@lewing @pranavkm @marek-safar @danroth27 @montyclt @jeffschwMSFT @Dotnet-GitSync-Bot