ar0311

The 10651 referred to is the issue in the aspnet/AspNetCore repo, not mono's.

After some more playing around, adding the following to the Blazor Client project results in a successful compilation, although obviously a much larger publish size. `false` Also, might it be...

Issue still exists in preview 8. And interestingly, on preview 8 the `false` causes a wasm error in the browser and prevents the app even starting. (Something about JSInterop)

Wasm error output in Chrome console: ` blazor.webassembly.js:1 Uncaught (in promise) Error: Could not find method "EndInvokeJS" on type "Mono.WebAssembly.Interop.MonoWebAssemblyJSRuntime" at g (blazor.webassembly.js:1) at blazor.webassembly.js:1 at callRuntimeCallbacks (mono.js:1) at postRun...

Still refuses to compile the Client project under preview 9 without referencing Microsoft.Extensions.Logging in the csproj file. Wasm error seems to be gone now.

Still exists on rc1... (Using updated preview9 blazor packages per rc1 release notes)

Fixed, the shell enable option was not set in the default config. Is this something that should be turned on by default?

What do we do if we want powershell installed from PMC but to install SDK from jammy repo? Also removing and re-installing dotnet* and aspnetcore* did not fix the issue...

Same issue here Fixed here by adding the following to compose file: ``` healthcheck: test: ["CMD", "drill", "@127.0.0.11", "cloudflare.com"] interval: 60s timeout: 10s ```