search

cloudsmithconsulting / cds-for-code

VSCode extension for working with Microsoft Common Data Service (CDS)
MIT License
22 stars 3 forks source link

command 'cs.cds.controls.cdsExplorer.addEntry' not found #14

Open crysh51 opened 4 years ago

crysh51 commented 4 years ago

When i am trying click on + sign to add a connect,i am getting er: command 'cs.cds.controls.cdsExplorer.addEntry' not found. Reinstalled and still getting same issue.

CloudSmithBrandon commented 4 years ago

Thank you for submitting this issue.

From this report, this would be an indicator that the extension has not loaded correctly. We'll look into this here in an attempt to correlate telemetry data with what you're experiencing.

It would be helpful if we could determine:

  1. What OS and VSCode version are you using?
  2. If you reload VSCode after installing the extension, does this change?
  3. Can you share what's in the CloudSmith output window?
CloudSmithBrandon commented 4 years ago

Update: We were unable to find any relevant telemetry, again, a likely side effect of the extension not loading correctly (thusly it doesn't know how to send telemetry data back).

CloudSmithIra commented 4 years ago

Have you tried installing the extension and then reloading VS Code using the developer reload command? Or close out VS Code entirely after installation?

crysh51 commented 4 years ago

Hi Brandon, Please see my answers below

  1. What OS and VSCode version are you using? = Windows 10
  2. If you reload VSCode after installing the extension, does this change? = No, i reloaded the extension, restarted VS Code and still getting the same error
  3. Can you share what's in the CloudSmith output window? Where can i find the output window to see results?

On Fri, Apr 3, 2020 at 12:09 PM Ira Mellor notifications@github.com wrote:

Have you tried installing the extension and then reloading VS Code using the developer reload command? Or close out VS Code entirely after installation?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/cloudsmithconsulting/cds-for-code/issues/14#issuecomment-608527440, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG4WZ3R742QX6L334VFSOVTRKYCZ3ANCNFSM4LZYKWPA .

--

Thanks,

Sai K Printing emails kills trees. Print is murder!

CloudSmithIra commented 4 years ago

Hi @crysh51,

To find the CDS for Code output window, start by opening the integrated terminal

step1

Then click the output tab, making sure to select "CloudSmith CDS for Code" in the dropdown

step2

It would be helpful for us to see what was logged in there. If we can't come up with something from that, I would be happy to schedule a remote debugging session with you if you'll have the time.

Thanks, Ira

crysh51 commented 4 years ago

I can't see CloudSmith CDS for Code listed in the Terminal.

On Tue, Apr 7, 2020 at 12:34 PM Ira Mellor notifications@github.com wrote:

Hi @crysh51 https://github.com/crysh51,

To find the CDS for Code output window, start by opening the integrated terminal

[image: step1] https://user-images.githubusercontent.com/50055774/78694920-5f40d500-78cb-11ea-9ac3-169a4e7d9284.png

Then click the output tab, making sure to select "CloudSmith CDS for Code" in the dropdown

[image: step2] https://user-images.githubusercontent.com/50055774/78694994-7bdd0d00-78cb-11ea-9778-ca207152fb8e.png

It would be helpful for us to see what was logged in there. If we can't come up with something from that, I would be happy to schedule a remote debugging session with you if you'll have the time.

Thanks, Ira

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cloudsmithconsulting/cds-for-code/issues/14#issuecomment-610491631, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG4WZ3TEV7YYFJ6VAMPHNZDRLNIZLANCNFSM4LZYKWPA .

--

Thanks,

Sai K Printing emails kills trees. Print is murder!

CloudSmithIra commented 4 years ago

I'm sorry to hear that.

At this time we are unable to reproduce this error on our local builds. If you have availability, we can set up a screen sharing session to step through this on your machine to triage the problem. To do so, please send an email to support@cdsforcode.com referencing Github issue #14 and we will be happy to coordinate.

We would love to spend some time to get this resolved.