You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue came up as part of Blazor's bottom-up planning. It would be great if we had a comparable experience profiling performance and memory for .NET WebAssembly apps as other .NET Core apps.
The text was updated successfully, but these errors were encountered:
Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.
Issue Details
This issue came up as part of Blazor's bottom-up planning. It would be great if we had a comparable experience profiling performance and memory for .NET WebAssembly apps as other .NET Core apps.
Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.
Issue Details
This issue came up as part of Blazor's bottom-up planning. It would be great if we had a comparable experience profiling performance and memory for .NET WebAssembly apps as other .NET Core apps.
This issue came up as part of Blazor's bottom-up planning. It would be great if we had a comparable experience profiling performance and memory for .NET WebAssembly apps as other .NET Core apps.
The text was updated successfully, but these errors were encountered: