Extension Conflict(s) - Local/Marketplace.

[MrDwarf7]

Describe the bug
If you have the VS Code extension installed BEFORE installing the .VISX file from the website tutorial, and you load the extensions via the .VISX file AS WELL, the two instances cause a conflict and VS code seemingly defaults to rendering NOTHING in the extension panel and won't load any of them.
Whenever the editor is reloaded (Whether because of "Reload required", or just closing and re-opening) it will act as if it has "uninstalled" the extension/not show up.

To Reproduce

1. Blank VS Code instance.
2. Download CodeTogether extension from marketplace.
3. Join a team, then follow the website prompts. One of which is to install a provided VISX extension.
4. Install it following the direction, and realize it broke your extensions and it now longer appears.
5. Install the extension from marketplace, reload as requested.
6. Realize the extension has mysteriously "uninstalled" itself.
7. Repeat steps 5 and 6 in a never-ending loop.

Expected behavior
That it would work/logic would default to referencing one of the two installed instances (And preferably correcting any clashes)

Screenshots
If applicable, add screenshots to help explain your problem.

CodeTogether Host

• IDE: VSCode
• IDE Version: 1.81.0 (user setup)
• OS: Windows
• OS Version: Windows_NT x64 10.0.22621

IDE Participant
-NUL for current issue.

Browser Participant
-NUL for current issue.

Additional context
-NUL for current issue.

Workaround (if any)
The solution to this, is to load up a new window, install the extension from the marketplace, then UNINSTALL IT, and do the reload it asks you to do.
After you have uninstalled and done the reload, it will still be present in your extensions pane.
This is, presumably, the local copy of the extension no longer clashing with the marketplace downloaded version (IE: You've "uninstalled" the marketplace version, of whichever one takes precedence in uninstall order).
To ensure this I also did an uninstall of that one, and a reload/Full exit cycle and it remained deleted.
Then re-installed it, this works as intended now, as I ONLY have the marketplace version installed.

I suggest updating the docs/the website walkthrough as it will likely cause others issues and be a pain.

[brianvfernandes]

Can appreciate how frustrating it must have been to run into this, and figure out how to get it resolved - thank you for posting the workaround. We'll consider updating both the documentation and the extension.

[MrDwarf7]

No problem, happy to help and hopeful to see it implemented. :)