I want to install an extension on a server without access to the internet, so I downloaded the vsix file and tried to install it on the server. Turns out that the VS code on the server is an old version, 1.59 if I remember correctly.
How can I find the vsix version that can be installed on a particular VS Code version.
I have been looking at the Github page for the extension but not an easy task to match extension version to VS Code version.
Related
I've published a VSCode extension.
Some users requested that I lower the minimum required VSCode engine version so that they can install the extension. https://code.visualstudio.com/api/working-with-extensions/publishing-extension#visual-studio-code-compatibility
The extension is a VSCode Web extension (works on both local VSCode and vscode.dev).
It looks like the VSCode Web was officially released along with VSCode v1.62.0.
But that does not necessarily mean that my extension won't work in, say v1.53.0.
So, what is the minimum VSCode version that supports Web extensions?
Another reason I want to lower the version is that some of my users might be using Eclipse Theia (VSCode fork) which lags behind the VSCode versions.
Is there a possibility to instal "Visual Studio Code" offline ? (with no Internet connection)
Best Regards
You can easily download the official installer from
https://code.visualstudio.com/download# (I took the System Installer version)
Therefore download the binaries on another machine.
Extensions can be installed from visx file.
https://marketplace.visualstudio.com/items?itemName=ms-vscode.powershell
extension name can bee looked up in VSCode itself:
VS Code extension identifier
Then install the extension.
where to find the button
That should be IMHO enough.
You surely already managed to install VS Code. For people who google a solution this could be helpful.
When I have everything configured in Visual Code I get the following error:
But my version of TFS is 2017, has someone else happened this?
Thanks
Assuming you want to install Azure Repos Extension for Visual Studio Code. First, you will need to install Visual Studio Code 1.12.0 or later.
Second, the extension uses your local repository information to connect to either Azure DevOps Services or Team Foundation Server 2015 Update 2 (and later). Please check whether the repository you open connected to appropriate TFS version.
Third, if you use TFVC, check whether you have the correct path of tf.exe.
Last, try to reinstall the extension and restart Visual Studio Code.
I am developing my VS Code extension. Old version is 1.0.0. I add a new feature which leverages VS Code's new feature Remote-development, which only available with VS Code engine version higher than 1.36.1. I added my extension new feature and upgraded my extension to 2.0.0.
I would like to restrict user's VS Code engine when installing my extension. If user would like to install my extension v2.0.0, he must have VS Code engine version higher than 1.36.1.
I set the minimum VS Code version restriction in extension's package.json file, engines fields, following VS Code Official Docs: Extension Manifest. But later I figured out that user with VS Code engine version lower then 1.36.1 still can search my 2.0.0 extension and install it. VS Code does not pop out any suggestion to inform user to upgrade their engine. And the extension can not work properly, of course.
// package.json
"engines": {
"vscode": "^1.36.1"
}
Did I miss something?
How can I restrict user with lower VS Code engine version either to upgrade their VS Code engine or install the old extension release?
Now user with lower VS Code engine version just install my new extension release and the extension can not work. Any help is appreciated!
I figured out the reason myself:
VS Code package.json's engines field does work. If user's engine lower than the required minimum engine version, VS Code will install lower version extension for user.
In my scenario, I have a dependency extension, whose engine requirement is not aligned with the main extension. This is the root cause of the main extension installation failure.
When user with lower version VS Code engine tries to install my extension, VS Code checks the dependency extension's engine requirement and fails to find a main extension release with proper dependency release. In this case, the installation of main extension fails.
Solution:
I have to find a way to remove my previous extension release from marketplace, whose engine requirement is not right.
My company is using an old CentOS6 and they wont update it before months (years?). This is totally out of my control and it obviously makes using up to date software a nightmare.
I would like to use Visual Studio Code as a C++ IDE but its intellisense plugin is running with glibc >=2.14 and Centos6 comes with glibc 2.12.
It also needed some more dependencies I managed to recompile and load with LD_LIBRARY_PATH. I tried compiling a new glibc and load it as well but it segfault, as expected.
I used the compiled version of VSCode from the official website.
I tried compiling it myself but it requires to download many files and my virtual machine does not have Internet, I can only transfer files through ftp. I created a local yarn repository, compiled all appropriate version of Yarn, NodeJS but a compiled binary is trying to download electron and I have no idea where to put the file to trick him into thinking it's downloaded already (assuming I could).
There are standalone solutions to run software on old distribution, like AppImage but VSCode is not part of their apps.
Would you have any idea on how to run VSCode on Centos6? Did you ever try to compile VSCode without and Internet Connection?
Currently the only viable solution I see would be to create an AppImage at home.
To run VS Code Server on CentOS 6, I followed the "glibc and libstdc ++ on RHEL / CentOS 6 update" article from here.
Perhaps this option will help you.