[release/6.0][wasm][debugger] Fix incompatibility between runtime and nuget package

[thaystg]

Customer Impact

When the customer created a project using release 6.0.0 and then install new versions of VS like: 6.0.2, the nuget package of the wasm project is not updated automatically, so the user uses the runtime 6.0.2 and the nuget package 6.0.0, the BrowserDebugProxy is inside this nuget package and one of our changes to show multidimensional array, caused this incompatibility.

Related Issues

https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1470864
https://dev.azure.com/devdiv/DevDiv/_workitems/edit/1484798

Testing

Manual testing

Risk

Very Low. This is just keeping the old behavior if the runtime is updated and the BrowserDebugProxy is not, so the multidimensional array will not work, but simple arrays will continue working.

[ghost]

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

Issue Details

---

Customer Impact

When the customer created a project using release 6.0.0 and then install new versions of VS like: 6.0.2, the nuget package of the wasm project is not updated automatically, so the user uses the runtime 6.0.2 and the nuget package 6.0.0, the BrowserDebugProxy is inside this nuget package and one of our changes to show multidimensional array, caused this incompatibility.

Testing

Manual testing

Risk

Very Low. This is just keeping the old behavior if the runtime is updated and the BrowserDebugProxy is not, so the multidimensional array will not work, but simple arrays will continue working.

Author:	thaystg
Assignees:	thaystg
Labels:	Servicing-consider, area-Debugger-mono
Milestone:	-

[lewing]

approved in email

[lewing]

wasm AOT failure is #66366

[ericstj]

@lewing what about the Mono Android x64 Release failures? Are those known?

[akoeplinger]

@ericstj yes those are infrastructure issues (the test app failed to install on the device), tracked by #65840