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

Support using environment variables in settings.json #8147

Closed
janegilring opened this issue Jun 26, 2016 · 3 comments
Closed

Support using environment variables in settings.json #8147

janegilring opened this issue Jun 26, 2016 · 3 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality
Milestone

Comments

@janegilring
Copy link

  • VSCode Version: 1.2.1
  • OS Version: Windows 10 (1511)

It would be nice to be able to use environment variables in paths in settings.json, this is not possible in build 1.2.1 and older.

In my scenariio I`m syncing VS Code settings between computers, for example:

// Specifies the path to a PowerShell Script Analyzer settings file. Use either an absolute path (to override the default settings for all projects) or use a path relative to your workspace.
"powershell.scriptAnalysis.settingsPath": "%home%.vscode\PSScriptAnalyzerSettings.psd1"

%home% is different on the computers VS Code is used on, thus it can`t be hardcoded.

@dbaeumer
Copy link
Member

@bpasero not sure who owns the settings service right now. May be it is @aeschli

@bpasero bpasero changed the title Using environment variables in settings.json is not possible Support using environment variables in settings.json Jun 27, 2016
@bpasero bpasero added the feature-request Request for new features or functionality label Jun 27, 2016
@bpasero bpasero added this to the Backlog milestone Jun 27, 2016
@dlebedynskyi
Copy link

I would really appreciate this feature for dotnet.
be default launch is picking up environment variable from ASPNETCORE_URLS' and dotnet run on this url. would be awesome to be able to specify this variable per process started

@bpasero
Copy link
Member

bpasero commented Jul 4, 2016

#2809

@bpasero bpasero closed this as completed Jul 4, 2016
@bpasero bpasero added the *duplicate Issue identified as a duplicate of another issue(s) label Jul 4, 2016
@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
*duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

4 participants