It seems that bumping System.Memory from 4.5.5 to 4.6.0 breaks our VS extension, which starts failing during parsing (which uses System.Memory) with:

Could not load file or assembly 'System.Memory, Version=4.0.2.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference.

We should probably revert that change (introduced by #18166 ) until we can resolve this issue in VS.