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

How do I enable extensions in the extensions dir in OSS Dev mode #23831

Closed
QwertyZW opened this issue Apr 3, 2017 · 4 comments
Closed

How do I enable extensions in the extensions dir in OSS Dev mode #23831

QwertyZW opened this issue Apr 3, 2017 · 4 comments
Assignees
Labels
license VS Code and component license issues *question Issue represents a question, should be posted to StackOverflow (VS Code)

Comments

@QwertyZW
Copy link
Contributor

QwertyZW commented Apr 3, 2017

master/

commit 6f42a236d521e9016a4d4fbf6aaf33cf3d9fad4e
Merge: 01d1e95 07ca248
Author: Daniel Imms <[email protected]>
Date:   Fri Mar 31 23:25:07 2017 -0700

    Merge pull request #23784 from DickvdBrink/patch-1

    Fixed typo in terminal.contribution description

Ubuntu 16.04

I'm trying to patch something in the vscode codebase,
I require the php extension to work in order for me to test my changes.
How do I enable all the extensions that ship with code in my config?

This is the config I'm using (just added runtime args to the original Launch Vs Code config)

		{
			"type": "chrome",
			"request": "launch",
			"name": "Launch VS Code",
			"windows": {
				"runtimeExecutable": "${workspaceRoot}/scripts/code.bat"
			},
			"osx": {
				"runtimeExecutable": "${workspaceRoot}/scripts/code.sh"
			},
			"linux": {
				"runtimeExecutable": "${workspaceRoot}/scripts/code.sh",
				"runtimeArgs": [
					"--extensions-dir", "${workspaceRoot}/extensions/"
				]
			},
			"urlFilter": "*index.html*"
		}

This does seem to cause the extension viewlet to list all the packages in the extension dir. But I still get this error when I launch my this config (Listen for Xdebug):

  "version": "0.2.0",
  // "debugServer": 4711, // Uncomment for debugging the adapter
  "configurations": [
    {
      "name": "Listen for XDebug",
      "type": "php",
      "request": "launch",
      "port": 9000,
      "log": true
    },
    {
      "name": "Launch",
      "request": "launch",
      "type": "php",
      "program": "${file}",
      "cwd": "${workspaceRoot}",
      "externalConsole": false
    }
  ]
}

error:
Configured debug type 'php' is not supported.

@QwertyZW QwertyZW changed the title How do I enable extensions in the extensions dir in dev mode How do I enable extensions in the extensions dir in OSS Dev mode Apr 3, 2017
@cleidigh
Copy link
Contributor

cleidigh commented Apr 3, 2017

@QwertyZW

The product.json for VSC OSS does not include the extension gallery URLs - see my example file below
I went through the same thing not sure why but are not supported as standard...

{
"nameShort": "Code - OSS",
"nameLong": "Code - OSS",
"applicationName": "code-oss",
"dataFolderName": ".vscode-oss",
"win32MutexName": "vscodeoss",
"licenseName": "MIT",
"licenseUrl": "https://github.com/Microsoft/vscode/blob/master/LICENSE.txt",
"win32DirName": "Microsoft Code OSS",
"win32NameVersion": "Microsoft Code OSS",
"win32RegValueName": "CodeOSS",
"win32AppId": "{{E34003BB-9E10-4501-8C11-BE3FAA83F23F}",
"win32AppUserModelId": "Microsoft.CodeOSS",
"win32ShellNameShort": "C&ode - OSS",
"darwinBundleIdentifier": "com.visualstudio.code.oss",
"reportIssueUrl": "https://github.com/Microsoft/vscode/issues/new",
"urlProtocol": "code-oss",
"extensionsGallery": {
"serviceUrl": "https://marketplace.visualstudio.com/_apis/public/gallery",
"cacheUrl": "https://vscode.blob.core.windows.net/gallery/index",
"itemUrl": "https://marketplace.visualstudio.com/items"
}
}

@isidorn
Copy link
Contributor

isidorn commented Apr 3, 2017

Thanks for answering @cleidigh
Yes you can enable the gallery like that and then you can install any extension you like.
You can also simply copy the whole extension into your user/code-oss-dev/.../extensions folder

@isidorn isidorn closed this as completed Apr 3, 2017
@isidorn isidorn added the *question Issue represents a question, should be posted to StackOverflow (VS Code) label Apr 3, 2017
@QwertyZW
Copy link
Contributor Author

QwertyZW commented Apr 4, 2017

Thanks!

@isidorn isidorn mentioned this issue May 29, 2017
@cristianhosu
Copy link
Contributor

I can confirm that the simplest solution is actually what @cleidigh said. At least for me on Linux

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
license VS Code and component license issues *question Issue represents a question, should be posted to StackOverflow (VS Code)
Projects
None yet
Development

No branches or pull requests

5 participants