Enhanced Security hinders performance of WASM applications (Including Blazor)
Hi, is there any official advice on what to do about "enhanced security" absolutely nuking performance of WASM? https://github.com/dotnet/aspnetcore/issues/48754 https://github.com/dotnet/aspnetcore/issues/56806 These existing tickets that were closed on the AspNetCore side, and it's been many years it seems and this is still an issue? I've submitted feedback through edge on this before but I have no way of knowing if this has been answered/looked at. We have a user who's required to have it on by policy and can't add it to the whitelist, and it's causing a pretty severe performance degradation. It just seems odd to me that the same company can produce two tools, and one of them absolutely breaks the other with seemingly no way to manage the downside at all.
--js-flags=--noexpose_wasm launch flag causes STATUS_BREAKPOINT
Version 135.0.3179.73 (Official build) (64-bit), Windows 11 Education, also occurs on Windows 10 Education and Windows 10 Pro, been testing this since probably version 129 of Edge. --js-flags=--noexpose_wasm as a launch flag causes STATUS_BREAKPOINT, this is regardless of default configuration and with or without extensions. WASM can be used to discover privileged information about a machine, and this seems to be working in the past according to some users online, but no longer does now. Please can someone advise?Building Real-Time Web Apps with SignalR, WebAssembly, and ASP.NET Core API
In this blog, we’ll explore how to build a real-time web application using three cutting-edge technologies: SignalR, WebAssembly, and ASP.NET Core API. SignalR simplifies the process of adding real-time web functionality, WebAssembly brings near-native performance to web apps, and ASP.NET Core API provides a robust and scalable backend. By combining these technologies, you can create web applications that are both highly responsive and performant.
