So I made a thing...

It's a VS Code extension based on Kirill Osenkov's @KirillOsenkov MS Build structured log viewer.

https://marketplace.visualstudio.com/items?itemName=lambdageek.msbuild-structured-log-viewer

The desktop version runs on CoreCLR, the https://insiders.vscode.dev version runs using the new (and still very experimental!) .NET 8 WASI workload on top of VS Code's WASI extension host (https://code.visualstudio.com/blogs/2023/06/05/vscode-wasm-wasi)

#vscode #dotnet #dotnet8 #net8 #wasi #coreclr #vscodeExtension #mono #msbuild #msbuildLogViewer #msbuildStructuredLogViewer #binlog

Experimental: MS Build Structured Log Viewer - Visual Studio Marketplace

Extension for Visual Studio Code - MS Build Structured Log Viewer displays the contens of MSBuild binary log files (.binlog) in a tree view

@lambdageek @KirillOsenkov

AAAA the WASI mode works so well too! I'm so excited to see an end-to-end .NET-on-WASI tool that's relevant to my day-to-day :)

@lambdageek (At least I think it does - I installed the WASI extension. How can I verify I'm running WASI only?)

@chethusk the WASI version pretty much only works on insiders.vscode.dev right now (it tries to install it for codespaces too, but it doesn't work because of some COI issues).

You can tell if it's running on CoreCLR or WASI by looking in the "MSBuild Log View" output window after you open a .binlog. if it says "opening msbuild log ... using .../dotnet" it's running on CoreCLR. If it says "opening msbuild log ... using Wasi runtime" it's the WASI version.

@lambdageek booo that's what I started thinking :) I see some chatter in the log about a wasm process sending/receiving messages - I'm guessing that's a backend implementation detail then?

@chethusk That's the log lying 😈

I need to change the logging strings to say "backend" instead of "wasm".

This whole project started out as wasm-first (mostly to see what was possible). The desktop version came later