Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[blazor] Remove reference to BINDING api in global namespace
See original GitHub issueThe blazor hotreload feature expects BINDING api to be exported to global namespace in the https://github.com/dotnet/sdk/blob/main/src/BuiltInTools/BrowserRefresh/BlazorHotReload.js.
The https://github.com/dotnet/aspnetcore/pull/46693 rewrote the invoke as a JSImport and with that we can call directly the async function receiveHotReloadAsync.
With the resolution of this issue we can remove disableDotnet6Compatibility: false from https://github.com/maraf/aspnetcore/blob/99a1d2c0cb39cbddb0e771d76c15fa96cae46261/src/Components/Web.JS/src/Platform/Mono/MonoPlatform.ts#L347
Issue Analytics
- State:
- Created 5 months ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
disableDotnet6Compatibility: falseis there also for 3rd party code which uses those global objects. Let’s flip it together with legacy interop when we link it out by default in the next major version (Net9).Confirmed, this is not necessary to be fixed in preview4.