Extension not working with VS17.3.3

[julealgon]

Describe the bug

After updating to VS 17.3.3, the extension does not appear in the list of installed extensions, and the OData connected service option is also missing in the Connected Services dialog.

When searching for the extension, VS tells me it is installed and I cannot uninstall/reinstall.

Version of the Project affected

ODataConnectedService v1.0.0
VisualStudio Version v17.3.3

Screenshots

Additional context

I had used the extension before very recently and it worked flawlessly for me.

[julealgon]

After closing Visual Studio and running devenv /setup as admin, it started working again. I have no idea why this was necessary however, so I don't know if this is a proper "fix" or not to the problem, so leaving it open for the team to consider.

[corranrogue9]

From triage: we should see if other extensions might have been having this issue recently. Also, @julealgon, was running as admin the second time different from the first? Can you help us understand any differences between the first update attempt (that didn't work) and the second update attempt (the one that succeeded)? We can probably try to repro this locally by using a recently updated vs instance and installing the extension.

[julealgon]

Also, @julealgon, was running as admin the second time different from the first? Can you help us understand any differences between the first update attempt (that didn't work) and the second update attempt (the one that succeeded)?

I had installed the extension recently (a few weeks ago) and tried it out right away. Worked without any problems.

Then I went to use it yesterday and noticed it was missing for some reason.

In-between these 2 tests, I updated Visual Studio.

Both of those executions were running VS as non-admin.

The only thing I did run as admin was the devenv /setup command, but that doesn't start Visual Studio after finishing. I ran the command, closed the console window, and then opened VS normally again (non-admin).

We can probably try to repro this locally by using a recently updated vs instance and installing the extension.

I think the issue happened after I updated VS having installed the extension in a previous version, so just installing the extension on the latest VS version directly wouldn't replicate it.