Runtime: Don't build if used any of not supported API
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
All 3 comments
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.
danroth27
on 29 Nov 2018
/cc @lewing. Having the portability analyzer would help here.
pranavkm
on 27 Jun 2020
This requires https://github.com/dotnet/designs/pull/110 approval
marek-safar
on 30 Jun 2020
Related issues
bencz
路
3Comments
omajid
路
3Comments
btecu
路
3Comments
v0l
路
3Comments
EgorBo
路
3Comments
Most helpful comment
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.