I'm looking to install an older version of the VSCode jupyter extension. (The reason is that I'm using a VSCode build from Code Server which is as of VSCode v1.57.1 - released this summer - and I'd like to install extensions for it). It looks like the Jupyter Extension version 2021.6.9999 is the newest version of the Jupyterhub plugin that supports VSCode version v1.57.1.
However, the marketplace only displays the last 5 extension versions under the "Version History" section of the landing page. These versions listed are all too new.
I'm able to find the source code for Jupyter version 2021.6.9999 on Github, but the vsix binaries are not there. I'm not sure how to compile it; seems like it'd be a pretty involved process.
Is there an archive of the vsix plugin files going back further than just 5 releases? Those versions were available earlier this year, so it seems like there should be a way to access the older vsix extensions somewhere. Any thoughts is much appreciated.
Marketplace not showing the older versions, but you can download .vsix files from marketplace anyway.
Copy below link and paste your browser, it will download jupyter
version 2021.6.999662501, you can download any vsix binary with this method, just change version name from URL.
https://marketplace.visualstudio.com/_apis/public/gallery/publishers/ms-toolsai/vsextensions/jupyter/2021.6.999662501/vspackage
Also, there is a site to download older vsix files: https://www.vsixhub.com/history/43174/
How can find the version number?
I research the source code and see version number format <year>.<month>.<build_number> from here: https://github.com/microsoft/vscode-jupyter/blob/main/CONTRIBUTING.md#versioning
GitHub Actions create releases and upload to marketplace when triggered. There is no human interaction. If you research Github Actions pipelines you can find version numbers. For an example:
https://github.com/microsoft/vscode-jupyter/runs/3765342614?check_suite_focus=true#step:7:169
A newer VSCode feature makes it easier.
Right click on the extension in the Extension tab. It will display an option "Install another version". From this menu you can install the desired version.
You can try
Go to https://web.archive.org/
Search for the package using original marketplace URL
Click on a date
Right click on download button and copy the URL
Remove everything before HTTPS://
Open remaining URL in browser
Cheers :)
Example
https://marketplace.visualstudio.com/items?itemName=AndersLaublaubplusco.SitecoreHelixVisualStudioTemplates
https://web.archive.org/web/20210116094649/https://marketplace.visualstudio.com/items?itemName=AndersLaublaubplusco.SitecoreHelixVisualStudioTemplates
https://marketplace.visualstudio.com/items?itemName=AndersLaublaubplusco.SitecoreHelixVisualStudioTemplates
search for respective date
Related
This page mentions VSCode 1.70.3 is the last release supporting Windows 7.
There's no download for that version listed at uptodown, and there's no tag for it in the github repository.
Where I can I download that version? What changed in it compared to 1.70.2 (e.g. this answer hints possibly something about PID in debug windows?), and where can I download the source code?
Here's a link that I've uploaded from my Temp folder after my VS Code was done updating: https://drive.google.com/file/d/1DRoY4c1lhoX9n0jM1Dy0tNr4Wks4CD74/view?usp=sharing
I am trying to install the ssh vscode extension offline by Install from VSIX. However, there is an error saying Unable to install extension 'ms-vscode-remote.remote-ssh' as it is not compatible with VS Code '1.39.2'. Is there a table in which I can get the correct match between my vscode and extensions?
There does not appear to be a table listing all of the versions for the Remote - SSH extension. The package does not include a changelog file, and the github page is just a placeholder for filing issues (so there's no useful history information there either).
However, the marketplace page has a "Version History" tab. That tab only lists the past five versions (0.55.0 to 0.62.0 at time of writing), but hovering the mouse on a link shows the URL pattern, so if you know or can guess the names of past versions then you can download them. For example, I guessed that 0.45.0 probably existed, and indeed it does: link to version 0.45.0.
Having downloaded the vsix file, you can unpack it by renaming the extension to zip and using any tool that understands the zip format (since that is what vsix is). Then check the package.json inside it to see which version it requires. In the case of 0.45.0, I see:
...
"engines": {
"vscode": "^1.36.0"
},
...
meaning that version works with VSCode 1.36.0 and (in theory) greater.
You could keep doing that, using binary search, to find the best match for your version of VSCode.
If you need to do this for another extension(s), and that extension does have a changelog file, it should be linked on the Version History tab as well as contained in the latest vsix package, and reading that may be easier than binary searching among downloads, depending on how it is written.
There is no "check for updates" when using the standalone/no install version.
What is best way to update a standalone version without losing settings etc.?
According to my experience (VSCode in a standalone .zip file uncompressed in D:\ using Win7 OS) you just need to download and uncompress the archive containing the new version (v 1.41.1).
When you run Code.exe in the new folder, your settings file is used and everithing is OK. (then, when you are really really sure that it is everithing OK, you could delete the old version).
If you changed the default settings file location, take a look at https://code.visualstudio.com/docs/getstarted/settings#_settings-file-locations
From the official doc it says when downloaded through zip file, one has download the release manually for each update and place the unzip version inside the Program files (Windows).
According to the special portable page all the settings, plugins, etc. of the standalone version
are stored in the data-folder. So assuming you called your vscode-folder vscode:
download the new version
unpack to vscode2 folder adjacent to current vscode
move data folder from vscode to vscode2
delete old vscode-folder
rename vscode2 to vscode
done
P.S.: Current portable versions notify about new version, but clicking on it leads to download, so above list still applies.
Edit 2020/08/04: To make a "normal" install portable one just needs to create the data folder inside the installation/unpack directory of VSC.
To download the old archive, replace user|system with archive in the URL.
Before:
https://update.code.visualstudio.com/1.69.2/win32-x64-user/stable
After:
https://update.code.visualstudio.com/1.69.2/win32-x64-archive/stable
When i trying update kentico to 10 version i have a some problem:
"the selected folder is missing a vital kentico component"
but I'm sure I chose the right folder. Who mean why?
It looks as if you are attempting to use the Kentico Hotfix Utility to upgrade from v9.0.50 to hotfix v10.0.41, which is not supported by Kentico. You cannot use the Kentico Hotfix Utility to upgrade Kentico from one major version to another. You need to:
First upgrade the project from 9.0.X => 10.0 - upgrade documentation available at https://docs.kentico.com/k10/installation/upgrading-to-kentico-10
Then you will need to run the project.
Then you can apply the latest hotfix utility - available at https://devnet.kentico.com/download/hotfixes
Then run the project again.
I appreciate you had a missing lib folder, but even if this were present, you still can't perform a major version upgrade using the hotfix utility.
I think in your case, you only have the CMS folder from deployment. But the upgrade needs the Lib folder which was not needed for deployment.
What you can do is to find the Lib folder from another instance or just install V9 of CMS, and you can find the missing Lib folder in C:\Program Files (x86)\Kentico\9.0\Webinstaller\Web
Few things can cause this:
Customized core files
Missing dll's
Changes in the web.config which cause Kentico references to be broken
and some other issues, but these are the most common we see.
Have you tried to open the project within Visual Studio and build the project? Secondly, are you selecting the directory with the CMS and Lib directory in it?
Does your project has the default structure or is it loke it was installed to the root of the web site? Default structure is some folder and underneath are the CMS, Lib and also the .sln file and few others. Looks like you have just the content of the CMS folder. In this case you either need the original project or upgrade the manual way.
You may also run CodeUpgrade tool from Kentico
Basic detection
Run CodeUpgrade.exe from the command line, with the path to your project’s solution file as the parameter (WebSite.sln or WebApp.sln).
For example:
CodeUpgrade.exe C:\inetpub\wwwroot\Kentico9\WebSite.sln
The tool generates a csv file containing a list of custom code occurrences in your project that are no longer valid in Kentico 10. The information will help you update your custom code after you perform the upgrade.
Source - Kentico documentation The documentation has all the commands to run and detect the incompatible code. This might help you.
Kentico 9 to 10 Upgrade tool - http://download.kentico.com/CMSUpgrades/Upgrade/Upgrade_9_0_10_0.exe
Basic steps to ensure before you perform upgrade - https://docs.kentico.com/k10/installation/upgrading-to-kentico-10
Has anyone tried to use the latest stats extension 1.3.1? I have tried, but when I unzip the file there is no stats.jar or stats.jar.gz files, like there was in the 1.2.1 version. If you have used it how did you get it to work?
I need it because it has a beta distribution function and is also easier to get up an running than the R extension (I have a locked down system).
The stats.jar file was missing from release v1.3.1. There is now a new release, v1.3.2, that contains stats.jar.
It seems like the jars have not been packaged with the currently available release at https://github.com/cstaelin/Stats-Extension/releases/tag/v1.3.1.
This is most likely a simple oversight from the author. I have opened an issue on GitHub.
In the meanwhile, you can still get an old jar from the git archive or try to build the extension yourself.