Surface better error and resolution steps when there is a platform architecture mismatch

[dibarbet]

Now that we package the server inside the extension, it is possible to get an ia32 server version on x64 platforms. This can cause issues when using an x64 version of .net (as the runtime installer as well will not download the ia32 version of dotnet).

We should surface a better error message (with a solution) instead of the current path platform mismatch error.

[winzig]

Does the "package the server inside the extension" feature you mention explain why code navigation features ("Go to Definition") have broken for me on macOS silicon this week?

Any recommendations on how to resolve?

[dibarbet]

Does the "package the server inside the extension" feature you mention explain why code navigation features ("Go to Definition") have broken for me on macOS silicon this week?

@winzig It's unlikely - if you were experiencing this issue you'd see pop-ups about the server failing to start (we've been packaing the server inside the extension since the start of 2.x).

We did upgrade some of our dependencies last week though to fix some dotnet resolution issues on MacOS with homebrew, so what you're hitting could be a fallout from that. Please file a new issue (via the csharp.reportissue command) with the C# logs attached (ideally with the dotnet.server.trace configuration to Trace).

[winzig]

@dibarbet Filed my issue here #6335