search

Power-Maverick / DataverseDevTools-VSCode

The all-in-one tool to develop code for Dataverse/Dynamics 365. Helps you connect to a Dataverse environment, generate TypeScript definitions for entities, create a different type of Dataverse-specific projects, and much more.
https://marketplace.visualstudio.com/items?itemName=danish-naglekar.dataverse-devtools
MIT License
55 stars 15 forks source link

[Bug]: Error on every command: Command not found on latest vsCode version #134

Closed Harl3 closed 11 months ago

Harl3 commented 11 months ago

What happened?

The extension stopped working after updating to the latest VsCode version, every button clicked gives a "command not found" error, for example trying to refresh connections:

dvdt.explorer.connections.refreshConnection: command 'dvdt.explorer.connections.refreshConnection' not found. This is likely caused by the extension that contributes dvdt.explorer.connections.refreshConnection.

I had to revert to VsCode 1.82 to restore a working version of the extension

image

What version of the tool are you using?

v2.1.4

What version of Visual Studio Code are you running?

1.83

Any relevant session id from VSCode?

No response

Relevant log output

dvdt.explorer.connections.refreshConnection: command 'dvdt.explorer.connections.refreshConnection' not found. This is likely caused by the extension that contributes dvdt.explorer.connections.refreshConnection.
power-maverick-bot[bot] commented 11 months ago

Thanks for opening your first issue here! Please make sure you have given us as much context as possible. One of the repo maintainer will respond as soon as possible.

0xNinshu commented 11 months ago

I am also facing this issue.

Power-Maverick commented 11 months ago

I will look into it this weekend. Thanks for letting me know.

Power-Maverick commented 11 months ago

I hope the issue has been resolved. Upgrade to v2.1.5. Please lemme know if you are running into issues.

Power-Maverick commented 11 months ago

Not resolved.. WIP

Power-Maverick commented 11 months ago

Issue should be resolved now. Make sure that v2.1.10 is installed.