Just started getting following error, when I open Powershell Script in Visual Studio Code. It was working fine till yesterday.
Here is the error:
The language service could not be started:
Error: The language client requires VS Code version ^1.26 but recevied version 1.25.1
I googled it found a page which said to change package.json file to older version, but I cant find that file, I am using a macos.
Your problem is incompatible versions. The PowerShell extension is using a later feature in vscode that is not available in the version you have installed.
You can:
Upgrade vscode (if auto-update is failing, you can download the installer and re-run it)
Downgrade the PowerShell extension
Use the latest VSIX that worked for you
Use Extensions: Install from VSIX... from the Command Palette (CTRL+SHIFT+P) in vscode
Turn off auto-update on your extensions by adding the following to settings.json:
"extensions.autoUpdate": false,
Related
I run the latest Visual Studio Code (1.56.1 windows 10 professional, as of today) but the jupyter extension file ms-toolsai.jupyter-2021.6.832913620.vsix complains with:
Unable to install extension 'ms-toolsai.jupyter' as it is not compatible with VS Code '1.56.1'.
How do I find out what is the latest version of jupyter compatible with VSC stable?
The latest compatible build of the Jupyter extension for VS Code 1.56.1 is 2021.6.832593372. v2021.6.832913620 requires VS Code 1.57.0-insider.
Unfortunately the VS Code marketplace doesn't currently indicate which version of VS Code you need to install a specific VSIX. There's a feature request for this: https://github.com/microsoft/vsmarketplace/issues/43. In the meantime it's recommended to install extensions from inside VS Code wherever possible, as VS Code version requirements are correctly resolved from there.
Latest version (2021.6.914258744) seems broken, but this one 2021.6.832593372 works.
Working setup as of June 9, 2021 (full offline install):
VSCode-win32-x64-1.56.2.zip
SHA1: 7F9DA2C7A35BA29778ECB36A2D3D81CBCCD3060D
ms-toolsai.jupyter-2021.6.832593372.vsix +
ms-python.python-2021.5.842923320.vsix = OK SHA1:
6D42F2306CCC870619FD058A09AA267FE33792DE
ms-toolsai.jupyter-2021.6.914258744.vsix +
ms-python.python-2021.5.842923320.vsix = Broken SHA1:
EF6FAB40ADB57894D169AD1E5811D19573E2F3C4
I am using a custom build version of the Visual Studio Code. It seems some extensions are checking the exact build name and version of the vscode before installation and if it doesn't match, vscode throws an error:
Unable to install because, the extension '....' compatible with
current version '...' of VS Code is not found.
For example, the Remote - SSH extension on my current custom build throws:
Unable to install because, the extension 'ms-vscode-remote.remote-ssh'
compatible with current version '1.32.0' of VS Code is not found.
Is there a way to bypass the version checking and force vs-code to allow the installation?
Issues
There are two issues to concern:
The first one is a legal one. The Remote - SSH extension's license is very restrictive. From its license:
You may use a copy of the software with each validly licensed copy of Microsoft Visual Studio Code. You may not use the software if you do not have a license for Microsoft Visual Studio Code.
The second one is the extension's incompatibility. It seems that your custom build is based on VS Code version 1.32.0. However, the initial release of the SSH extension requires at least VS Code 1.35.0 or above. From the release notes of VS Code 1.35.0:
The Remote Development extensions are now available for VS Code Stable [...]
Conclusion
So even if you do not care about the legal issues and are able to force install the extension for your custom build it will probably not work since the extension requires a more recent release of VS Code.
More information on this topic can be found in the VSCodium documentation (A "free version" of VSCode). If you rely on the SSH extension and consider switching your custom build, there you will find a possible workaround to get the remote extensions working with VSCodium (I haven't tested it on my own).
I have Visual Studio Code installed in Ubuntu 20.04. I love how it works. I installed it from the tar ball. Same with the SDK. I just found that those appear to work better than installing from deb packages.
I created a desktop file so I could add Visual Studio Code to the dock and launch it that way, but what I've noticed is that projects won't compile. I get errors stating it can't find the project even though the errors are listing the folder where the items exist.
The only way I can get it to work is to:
Open a terminal.
Navigate to the folder where the project files reside.
Launch code from the command line.
Then it works. Otherwise, I get a pop-up error that says "The preLaunchTask 'build' terminated with exit code -2" and then the terminal window is filled with errors.
Here's the last of the error messages and then I opened up a terminal and it shows that I'm in the folder for the project and the csproj exists there:
This also happens if I install Visual Studio code from a repository. It seems launching it from the Unity desktop breaks something. But if I launch it from the command line in a terminal session from the folder where the project resides, then the problem goes away.
I can also reproduce this error from the command line if I launch Visual Studio Code from a different folder than the project I'm trying to compile.
Is this common? Just curious. I'm wondering if because when I launch it from the Unity desktop, it's launching under a different
I got it working under 20.04. I must have done something wrong so I did a wipe of the .NET Core install and reinstalled it all using the bash shell script and then was able to install Code via Software Installer tool. Not sure why it didn't work before, but it works now.
I am unable to get Python extension working with fresh install of VS Code / Python 3.7.3 on Windows 10.
VS Code status bar shows a message 'Python extension loading...' continuously.
Python is installed in a non-standard path at c:\Programs\Python\Python37-32\python
Have uninstalled both VSCode and python several times and had installed afresh.
C:\WINDOWS\system32>which python
/c/Programs/Python/Python37-32/python
When developer tools is opened, the following error shows up in console.
property 'length' of undefined
at g.update (c:\Users\APCIT\.vscode\extensions\ms-python.python-2019.4.11987\out\client\extension.js:83:373818)
at g.initialize (c:\Users\APCIT\.vscode\extensions\ms-python.python-2019.4.11987\out\client\extension.js:83:381134)
at new g (c:\Users\APCIT\.vscode\extensions\ms-python.python-2019.4.11987\out\client\extension.js:83:372522)
at Function.getInstance (c:\Users\APCIT\.vscode\extensions\ms-python.python-2019.4.11987\out\client\extension.js:83:372729)
at h.getSettings (c:\Users\APCIT\.vscode\extensions\ms-python.python-2019.4.11987\out\client\extension.js:83:370264)
at b.initialize (c:\Users\APCIT\.vscode\extensions\ms-python.python-2019.4.11987\out\client\extension.js:83:624877)
at c:\Users\APCIT\.vscode\extensions\ms-python.python-2019.4.11987\out\client\extension.js:9:93210
at c:\Users\APCIT\.vscode\extensions\ms-python.python-2019.4.11987\out\client\extension.js:9:93877
at module.exports.t.activate (c:\Users\APCIT\.vscode\extensions\ms-python.python-2019.4.11987\out\client\extension.js:9:96601)
at Function._callActivateOptional (c:\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:719:166)
at Function._callActivate (c:\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:718:872)
at define._doActivateExtension.Promise.all.then.e (c:\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:718:79)
(Posted solution on behalf of the question author).
OK - I deleted the VS Code profile folder
'%APPDATA%\Roaming\Code
and installed fresh extension along with miniconda, and it is working fine.
This seems to be an annoying problem that is caused by other extensions. Best way I fixed mine was:
To disable all the extensions
Enable ms-python extension
Reload vs-code and voila, it's all fixed
I also had this problem. But I fixed it by changing the location of the python file.
Just downloaded Nov version 1.8.1, Windows 10 VS Code.
Opens up fine. I try installing any Extension, it just hangs, says Installing.
Never installs any extensions.
I tried making the .vsix path readable, i tried version 1.7, I tried uninstalling, re-installing.
I tried adding the core, removing the core, the SDK, removing the SDK, I tried running as Admin.
Nothing worked.
This worked for me
In the .vscode\extensions directory i found a file called obsolete and deleted it and was able to install extensions manually downloaded via VSIX