* Initialize the runtime state correctly for debugging On startup the DebugProxy needs to know when the runtime has initialized enough to be able to begin interaction this is accomplished by breaking in mono_wasm_runtime_ready() which the Proxy sees does initialization and then resumes from. Simply setting mono_wasm_runtime_is_ready breaks that logic, but even worse it appears that the variable is linked out in the release version * Regen webassembly.js Co-authored-by: Larry Ewing <lewing@microsoft.com> |
||
|---|---|---|
| .. | ||
| Analyzers | ||
| Antiforgery | ||
| Azure | ||
| Components | ||
| DataProtection | ||
| DefaultBuilder | ||
| Features/JsonPatch | ||
| Framework | ||
| Hosting | ||
| Html/Abstractions | ||
| Http | ||
| Identity | ||
| Installers | ||
| Middleware | ||
| MusicStore | ||
| Mvc | ||
| ProjectTemplates | ||
| Razor | ||
| Security | ||
| Servers | ||
| Shared | ||
| SignalR | ||
| SiteExtensions | ||
| Tools | ||
| submodules | ||