Skip to content

Conversation

@lambdageek
Copy link
Member

We initially added support for creating sessions from JS to validate that EP was functional before we had the WebSocket-based diagnostic server. Now we don't need that stuff anymore.

Also remove the browser-mt-eventpipe sample. The browser-threading and browser-eventpipe samples are the replacements - they do one thing at a time instead of collecting all the experimental cruft

use the websocket diagnostic server support instead
use the browser-threading sample for working with threading
use the browser-eventpipe sample for working with tracing
@ghost
Copy link

ghost commented Aug 8, 2022

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

@ghost ghost assigned lambdageek Aug 8, 2022
@lambdageek lambdageek added area-Diagnostics-mono arch-wasm WebAssembly architecture labels Aug 8, 2022
@ghost
Copy link

ghost commented Aug 8, 2022

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

We initially added support for creating sessions from JS to validate that EP was functional before we had the WebSocket-based diagnostic server. Now we don't need that stuff anymore.

Also remove the browser-mt-eventpipe sample. The browser-threading and browser-eventpipe samples are the replacements - they do one thing at a time instead of collecting all the experimental cruft

Author: lambdageek
Assignees: lambdageek
Labels:

arch-wasm, area-Diagnostics-mono

Milestone: -

@lambdageek lambdageek merged commit f195918 into dotnet:main Aug 9, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Sep 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

arch-wasm WebAssembly architecture area-Diagnostics-mono

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants