[wasm][debugger] Check client version to send debugger message

[thaystg]

PR #86982 changed the response format for the MDBGPROT_CMD_GET_ASSEMBLY_BYTES in the debugger-agent, to send only the asm metadata instead of the full assembly contents.

But the PR missed adding appropriate version checks for the new format to keep backward compatibility. And this broke when a older proxy which didn't understand the new format was used with the updated runtime.

      Failed to load https://localhost:7284/_framework/Microsoft.AspNetCore.Authorization.wasm (Stream does not contain a valid Webcil file) (stack=   at Microsoft.NET.WebAssembly.Webcil.WebcilReader..ctor(Stream stream)
         at Microsoft.WebAssembly.Diagnostics.AssemblyInfo.FromBytes(MonoProxy monoProxy, SessionId sessionId, Byte[] assembly, Byte[] pdb, ILogger logger, CancellationToken token)
         at Microsoft.WebAssembly.Diagnostics.DebugStore.Load(SessionId id, String[] loaded_files, ExecutionContext context, Boolean useDebuggerProtocol, CancellationToken token)+MoveNext())

With this change I'm adding the needed version guards when sending the response. And bumping the BrowserDebugProxy version, so it can correctly get the newer format response.

Fixes https://github.com/aspnet/AspNetCore-ManualTests/issues/2236

[ghost]

Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Checking that BrowserDebugProxy is waiting for this new format to avoid incompatibility

Author:	thaystg
Assignees:	-
Labels:	area-Debugger-mono
Milestone:	-

[radical]

Could you please explain what was the issue here? And how it is being fixed?

[thaystg]

Could you please explain what was the issue here? And how it is being fixed?

Runtime has a newer version and BrowserDebugProxy is older, then runtime was sending a different message format and BrowserDebugProxy was crashing.
With this change I'm bumping the BrowserDebugProxy version and checking the BrowserDebugProxy version on runtime side to decide the message format before send it.

[radical]

Could you please explain what was the issue here? And how it is being fixed?

Runtime has a newer version and BrowserDebugProxy is older, then runtime was sending a different message format and BrowserDebugProxy was crashing. With this change I'm bumping the BrowserDebugProxy version and checking the BrowserDebugProxy version on runtime side to decide the message format before send it.

Could you please add that to the PR description?

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

PR #86982 changed the response format for the MDBGPROT_CMD_GET_ASSEMBLY_BYTES in the debugger-agent, to send only the asm metadata instead of the full assembly contents.

But the PR missed adding appropriate version checks for the new format to keep backward compatibility. And this broke when a older proxy which didn't understand the new format was used with the updated runtime.

      Failed to load https://localhost:7284/_framework/Microsoft.AspNetCore.Authorization.wasm (Stream does not contain a valid Webcil file) (stack=   at Microsoft.NET.WebAssembly.Webcil.WebcilReader..ctor(Stream stream)
         at Microsoft.WebAssembly.Diagnostics.AssemblyInfo.FromBytes(MonoProxy monoProxy, SessionId sessionId, Byte[] assembly, Byte[] pdb, ILogger logger, CancellationToken token)
         at Microsoft.WebAssembly.Diagnostics.DebugStore.Load(SessionId id, String[] loaded_files, ExecutionContext context, Boolean useDebuggerProtocol, CancellationToken token)+MoveNext())

With this change I'm adding the needed version guards when sending the response. And bumping the BrowserDebugProxy version, so it can correctly get the newer format response.

Fixes https://github.com/aspnet/AspNetCore-ManualTests/issues/2236

Author:	thaystg
Assignees:	thaystg
Labels:	arch-wasm, area-Debugger-mono
Milestone:	-