Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Command "Extensions: Install Extension" missing when running vscode from source #2647

Closed
vizeke opened this issue Feb 2, 2016 · 9 comments
Closed

Comments

@vizeke
Copy link

vizeke commented Feb 2, 2016

I'm trying to test the install plugin feature in the latest pre-release 0.10.7 but it doesn't show up.

vscode_install_extension

I just cloned the repo and follow the steps to run vscode. I'm using Windows 8.1 x64

Am I missing something?

@egamma
Copy link
Member

egamma commented Feb 2, 2016

If you build VS Code from source then the product is configured without some features like the extensins gallery. Pls see this comment for more background on this #60 (comment)

If you install the published Insider version then the command is there. Pls see
https://blogs.msdn.microsoft.com/vscode/2016/02/01/introducing-insiders-builds/

@mucaho
Copy link

mucaho commented Apr 1, 2016

I've done some digging and figured out how to install an extension manually. There may be a better way to do this, but can't find any documentation on it:

EDIT: Aha, yes, one more important thing: I can't speak for anyone here, but I guess once you start using MS's branded services, e.g. loading extensions from the gallery store, you agree to their terms of use. I'd imagine that installing these extensions also applies under the proprietary Visual Studio Code license, as well as any individual license contained in the extension.

@jgillich
Copy link

jgillich commented Apr 1, 2016

@egamma Can you please elaborate, is it possible to build VS Code with the extension gallery or is that a closed source component?

@egamma
Copy link
Member

egamma commented Apr 2, 2016

@jgillich this has already been elaborated here #60 (comment), hasn;t it?

@jgillich
Copy link

jgillich commented Apr 2, 2016

@egamma Well, given how vital extensions are to a editor like VS Code, I couldn't quite believe what I read and had to ask for confirmation.

@mucaho
Copy link

mucaho commented Apr 3, 2016

@jgillich I think there has been a slight misunderstanding: If you read one of the following comments in #60, it says that you just need to modify a configuration file for it to work.
I've just added 3 lines to the configuration file and that enabled the extension manager!

@jgillich
Copy link

jgillich commented Apr 4, 2016

@mucaho Seems so, thanks! Now I'm relieved.

@robertolabarca
Copy link

  1. Ir a https://vscode.blob.core.windows.net/gallery/index y localizar la entrada correspondiente a la extensión que se quiere instalar . Esta url es un cache de todas las extensiones disponibles en la galeria
  2. Localizar el assetUri para la version deseada
  3. Agregar /Microsoft.VisualStudio.Services.VSIXPackage?install=true al assetUri y descargar la url resultante (ej: "assetUri":https://ms-vscode.gallery.vsassets.io/_apis/public/gallery/publisher/ms-vscode/extension/csharp/1.4.1/assetbyname

Url resultante : https://ms-vscode.gallery.vsassets.io/_apis/public/gallery/publisher/ms-vscode/extension/csharp/1.4.1/assetbyname/Microsoft.VisualStudio.Services.VSIXPackage?install=true
)
4. Renombrar el fichero Microsoft.VisualStudio.Services.VSIXPackage descargado en 3 a Microsoft.VisualStudio.Services.VSIX.
5. Ejecutar code --install-extension Microsoft.VisualStudio.Services.VSIX
6. Ejecutar tareas pos instalación. Solo de ser necesario por el componente.

@robertohuertasm
Copy link
Contributor

Just to make it simple:

  1. Find product.json file
  2. Add the following lines to it:
"extensionsGallery": {
  "serviceUrl": "https://marketplace.visualstudio.com/_apis/public/gallery",
  "cacheUrl": "https://vscode.blob.core.windows.net/gallery/index",
  "itemUrl": "https://marketplace.visualstudio.com/items"
}

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants