I believe it’s due to updating the debugger, and pointing to a new C#/Omnisharp VS code extension. I have a workaround here:
3 Likes
I believe it’s due to updating the debugger, and pointing to a new C#/Omnisharp VS code extension. I have a workaround here: