[release/6.0][wasm][debugger] Fix incompatibility between runtime and nuget package #66301
Conversation
|
Tagging subscribers to this area: @thaystg Issue DetailsCustomer ImpactWhen 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. TestingManual testing RiskVery 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.
|
lewing
added
Servicing-approved
|
approved in email |
|
wasm AOT failure is #66366 |
|
@lewing what about the |
ghost
locked as resolved and limited conversation to collaborators
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.