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
Related
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 am struggling to get Ballerina working with Visual Studio Code (on Windows 10).
It is installed and works fine from Command Prompt, however it cannot complete build command in Visual Studio Code. It does not seem to be able to finish build command effected via Visual Studio Code. I have Ballerina extension for Visual Studio Code installed.
Does anybody had similar problems and know how to overcome it?
Bellow please find details of versions:
Ballerina 1.2.1
Language specification 2020R1
Ballerina tool 0.8.5
VSC:
1.44.2
Ballerina extension for Visual Studio Code
Windows:
10 Pro
Version 10.0.18362
#GregorSind, try quitting the VSCode instance and then reopen. This might be that the environment variables are not being visible to the VSCode instance. Also, check what's the integrated shell of VSCode
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 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,
I am using v 1.23.1 on windows 7
When I open visual code there are no other windows for the app that will show. If I Open a folder it will not show the code. If I click on File > Preferences > Settings it will not open the window (I assume a modal). I have uninstalled it several time, and removed everything out of %appdata% code. It has worked in the past, but it might have been a previous version.
I can't get to the remove extensions window to remove extensions
Version 1.23.1
Commit d0182c3
Date 2018-05-10T17:11:17.614Z
Shell 1.7.12
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64.
I had to do this to make it work
code --disable-gpu
As Microsoft said:
https://code.visualstudio.com/docs/supporting/FAQ#:~:text=Microsoft%20ended%20support%20for%20Windows,later%20versions%20of%20VS%20Code.
Can I run VS Code on Windows 7?
Microsoft ended support for Windows 7 in January, 2020 and no longer provides security updates. VS Code desktop versions starting with 1.71 (August 2022) will no longer run on Windows 7 and you will need to upgrade to a newer Windows version to use later versions of VS Code.
VS Code will no longer provide product updates or security fixes on Windows 7 and VS Code version 1.70.3 is the last available release for Windows 7 users. You can learn more about upgrading your Windows version at support.microsoft.com.
I was getting the same issue so I downloaded the 1.70.2 and it started working.
https://code.visualstudio.com/updates/v1_70
https://update.code.visualstudio.com/1.70.2/win32-x64-user/stable
Follow these for permanent solution:
right click the visual studio icon on desktop
go to properties
go to the path
after the end of inverted commas"..
give a blankspace and type: --disable-gpu
press apply and ok
restart now.