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.

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

[release/5.0] Backport Browser Unsupported Attribute Changes #41967

Conversation

mdh1418
Copy link
Member

@mdh1418 mdh1418 commented Sep 8, 2020

An ongoing effort in #41087 to mark APIs as unsupported on Browser led to many PRs being created with each targeting a unique namespace. Rather than back porting on every single one of those PRs, this PR intends to back port all of those merged changes as one batch.

It is expected that more PRs will be created and merged today, and those will also be added to this PR.

mdh1418 and others added 8 commits September 8, 2020 11:12
…net#41094)

* [wasm] System.ComponentModel enable platform attributes

* [wasm] Mark ExtendedProtectionPolicyTypeConverter.ConvertTo as unsupported

* [wasm] Mark System.ComponentModel.TypeDescriptor.CreateInstance as unsupported

* [wasm] Mark System.ComponentModel.TypeDescriptionProvider.CreateInstance as unsupported

* [wasm] Mark System.ComponentModel.LicenseManager.CreateWithContext as unsupported

* [wasm] Mark System.ComponentModel.MaskedTextProvider.Clone as unsupported

Co-authored-by: Mitchell Hwang <mitchell.hwang@microsoft.com>
* [wasm] Mark System.Console APIs as unsupported on Browser

* System.Console remove unsupported attribute from Console.Clear()

* System.Console mark SetIn as unsupported on Browser

* System.Console move UnsupportedOSPlatform attributes down to the accessor

Co-authored-by: Mitchell Hwang <mitchell.hwang@microsoft.com>
…tnet#41271)

Co-authored-by: Mitchell Hwang <mitchell.hwang@microsoft.com>
…#41694)

Co-authored-by: Mitchell Hwang <mitchell.hwang@microsoft.com>
…net#41683)

* [wasm] System.IO.Compression.Brotli enable platform attributes

* Mark System.IO.Compression.Brotli unsupported at assembly level

Co-authored-by: Mitchell Hwang <mitchell.hwang@microsoft.com>
…er (dotnet#41682)

* [wasm] System.IO.FileSystem.Watcher enable platform attributes

* Mark System.IO.FileSystem.Watcher unsupported at assembly level

Co-authored-by: Mitchell Hwang <mitchell.hwang@microsoft.com>
…otnet#41700)

* [wasm] System.IO.IsolatedStorage enable platform attributes

* Mark System.IO.IsolatedStorage Unsupported at assembly level

Co-authored-by: Mitchell Hwang <mitchell.hwang@microsoft.com>
…t#41891)

* System.Threading.ThreadPool enable platform attributes

* Mark System.Threading.ThreadPool APIs unsupported on browser

* System.Threading.ThreadPool Add Unsupported attribute to other ThreadPool files

* Remove Unsupported attributes from BindHandle

* Add windows Supported Attribute to BindHandle

Co-authored-by: Mitchell Hwang <mitchell.hwang@microsoft.com>
MaximLipnin and others added 2 commits September 8, 2020 19:28
… on Browser (dotnet#41963)

* Mark System.Net.WebSockets.ClientWebSocketOptions APIs as unsupported on Browser

* Add the attributes to non-browser version of ClientWebSocketOptions class to avoid build error

* Add using

* Include platform attributes
…otnet#41985)

Co-authored-by: Mitchell Hwang <mitchell.hwang@microsoft.com>
@marek-safar marek-safar added arch-wasm WebAssembly architecture Servicing-consider Issue for next servicing release review labels Sep 9, 2020
@mdh1418 mdh1418 merged commit e032f4f into dotnet:release/5.0 Sep 9, 2020
mdh1418 pushed a commit to mdh1418/runtime that referenced this pull request Sep 10, 2020
@mdh1418 mdh1418 deleted the mdhwang/backport_browser_unsupported_API_attributes branch September 11, 2020 15:41
@ghost ghost locked as resolved and limited conversation to collaborators Dec 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly architecture area-Meta Servicing-consider Issue for next servicing release review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants