You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
We are using Code in an offline setting and we are relying on downloading extensions from the marketplace.
For that workflow, it would be very nice to have the required engine version in the version history on the marketplace to avoid having to manually download and check the version only to realize that the required version does not match ours and download again.
As an example, the latest versions of Jupyter (https://marketplace.visualstudio.com/items?itemName=ms-toolsai.jupyter) require 1.59.0-insider and we had to check a few versions before finally finding the latest version compatible with 1.58.
Considering the required engine is listed in the manifest of the vsix package, I reckon it should not be too hard to automate the printing of the version, but I might be wrong.
This discussion was converted from issue #132 on August 10, 2021 12:02.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
We are using Code in an offline setting and we are relying on downloading extensions from the marketplace.
For that workflow, it would be very nice to have the required engine version in the version history on the marketplace to avoid having to manually download and check the version only to realize that the required version does not match ours and download again.
As an example, the latest versions of Jupyter (https://marketplace.visualstudio.com/items?itemName=ms-toolsai.jupyter) require 1.59.0-insider and we had to check a few versions before finally finding the latest version compatible with 1.58.
Considering the required engine is listed in the manifest of the vsix package, I reckon it should not be too hard to automate the printing of the version, but I might be wrong.
Beta Was this translation helpful? Give feedback.
All reactions