Hi, thanks for sharing this issue.
We've just tested this on the new preview build and it seems to be working on our end. I think this is an install state issue. Could you try the removal and reinstall fix described
here? I realise you've probably done many of these steps already with your manual installation, but we need to make sure they are done in a very specific order to reset VS's caches and install state.
The instructions above expect you to use the MSI, but if that doesn't work, I'm hoping that doing the full manual install after the described steps will sort it out.