aspnetcore/src
Pranav K 555cf52454
Initialize the runtime state correctly for debugging (#19426)
* 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>
2020-02-28 08:17:24 -08:00
..
Analyzers
Antiforgery
Azure
Components Initialize the runtime state correctly for debugging (#19426) 2020-02-28 08:17:24 -08:00
DataProtection
DefaultBuilder
Features/JsonPatch Update some tests 2019-11-05 11:24:48 -08:00
Framework Avoid copying the shared fx in blazor-wasm 2020-01-03 15:05:53 -08:00
Hosting
Html/Abstractions
Http [3.1.x] Backport HttpContext.Items fix (#17237) 2019-11-22 15:24:27 -08:00
Identity
Installers Download runtime from suffixed location in dotnetcli blob storage (#17592) 2019-12-05 12:33:38 -08:00
Middleware
MusicStore
Mvc
ProjectTemplates Stop service worker interfering with Identity UI (#19400) 2020-02-27 22:42:44 -08:00
Razor
Security
Servers [3.1.x] Allow external startup hooks (#17116) 2019-11-23 10:06:25 -08:00
Shared Blazor WebAssembly package renames (#19026) 2020-02-18 10:54:28 -08:00
SignalR
SiteExtensions
Tools Change how we resolve dotnet in tests (#16934) 2019-11-09 17:17:58 -08:00
submodules