VS Blazor editor

[danroth27]

• Make Razor code generation extensible (external)
• Component intellisense completions (at design time build)
• Blazor extending Razor code generation (including tooling)

[veikkoeeva]

@danroth27 What would be needed for this? I took a look at the How to contribute section and didn't spot what's needed compile the code into WASM modules. I'm guessing the process is described at https://github.com/lrz/mono-wasm. Is this true? If so, I could add a note of it to the contribution guide. It appears (offline chatting) more than a few people are pondering the process.

[danroth27]

@veikkoeeva The only WASM code currently is the .NET runtime itself, which is provided by our friends on the Mono team and is checked in here: https://github.com/aspnet/Blazor/blob/dev/src/mono/dist/unoptimized/wasm/mono.wasm.
This .NET runtime can then be used to run normal .NET assemblies in the browser. Blazor is a web UI framework implemented as normal .NET assemblies. If you're interested in how the Mono runtime is built into WebAssembly you'll need to look at the Mono repo.

[SteveSandersonMS]

@rynowak No rush to respond today, but do you think this is done enough that we should mark this high-level issue as done?

[rynowak]

Yep. Closing