Skip to content

Extension says its v 0.8.1 after installing 0.10.2 #602

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
julielerman opened this issue Sep 14, 2018 · 4 comments
Closed

Extension says its v 0.8.1 after installing 0.10.2 #602

julielerman opened this issue Sep 14, 2018 · 4 comments

Comments

@julielerman
Copy link

julielerman commented Sep 14, 2018

2018-09-14_08-26-30

I've uninstalled and reinstalled etc. Wondering if this is related to the debugging issues I'm having with node if I'm truly on 0.8.1.

@ejizba
Copy link
Contributor

ejizba commented Sep 14, 2018

You can try manually removing the extension from the following folder and then re-installing. I believe this is where it's located:

  • Windows: C:\Users\<user name>\.vscode\extensions\
  • Mac: ~/.vscode/extensions/

You can remove the whole folder named ms-azuretools.vscode-azurefunctions-<version>

@julielerman
Copy link
Author

that dd the trick. Maybe all of the other nonsense that's been happening will disappear. Back to more testing!! (wonders why it was stuck)

@ejizba
Copy link
Contributor

ejizba commented Sep 14, 2018

So I double checked your versions in the other thread and our extension relies on VS Code version "1.24.0" or greater and you were on "1.21.1". "0.8.1" must be the last version that supports "1.21.1".

I'm surprised VS Code doesn't warn you about that in any way. Feel free to file an issue on VS Code directly to improve that messaging (unfortunately we don't control how we're installed or anything related to the Extension marketplace)

Are you still on "1.21.1" after you got it working or did you update VS Code?

@julielerman
Copy link
Author

yeah ..just realized it still says 0.8.1 after all that. I've done "check for updates" so many times for vscode and it says "nope". Wow. Off to just unisntall reinstall

@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants