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.

Sign up for GitHub

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

Jump to bottom

Modify the terminal environment for MSVC #5271

Open
SuperWig opened this issue Apr 9, 2020 · 1 comment
Open

Modify the terminal environment for MSVC #5271

SuperWig opened this issue Apr 9, 2020 · 1 comment
Assignees
@bobbrow
Labels
Feature: Configuration An issue related to configuring the extension or IntelliSense Feature Request help wanted Can be fixed in the public (open source) repo. Language Service tasks/build/debug An issue relating to tasks.json (e.g. build issues) Visual Studio Code Caused by (or depends on changes from) VS Code
Milestone
On Deck

Comments

@SuperWig
Copy link

SuperWig commented Apr 9, 2020

If I'm not mistaken this should now be possible thanks to microsoft/vscode#46696

So it would be nice if there was a setting for the integrated terminal to be setup for MSVC without having to open VS Code through the developer command prompt or by other means.

Extension of #4178
@sean-mcmanus sean-mcmanus added this to the Tracking milestone Apr 9, 2020
@sean-mcmanus sean-mcmanus added tasks/build/debug An issue relating to tasks.json (e.g. build issues) Feature Request Feature: Configuration An issue related to configuring the extension or IntelliSense Visual Studio Code Caused by (or depends on changes from) VS Code help wanted Can be fixed in the public (open source) repo. labels Apr 9, 2020
@sean-mcmanus sean-mcmanus mentioned this issue Apr 15, 2020
Closed
@sean-mcmanus sean-mcmanus mentioned this issue May 6, 2020
Closed
@Colengms Colengms removed this from the Tracking milestone Oct 22, 2020
@bobbrow bobbrow added this to the Backlog milestone Apr 20, 2021
@sean-mcmanus sean-mcmanus mentioned this issue Sep 17, 2021
Closed
@jureid jureid self-assigned this Sep 20, 2021
@Colengms Colengms modified the milestones: Backlog, 1.8.0 Sep 21, 2021
@bobbrow bobbrow modified the milestones: 1.8.0, 1.9.0 Jan 11, 2022
@sean-mcmanus sean-mcmanus modified the milestones: 1.9, 1.10 Mar 8, 2022
@xq114
Copy link

xq114 commented Mar 21, 2022

Since VS Code doesn't support the feature now, I'd like to recommend xmake as an alternative. Installing xmake will allow you to launch a Visual Studio virtual environment by a simple command

xrepo env -b msvc shell

image

@sean-mcmanus sean-mcmanus modified the milestones: 1.10, 1.11 Jun 8, 2022
@bobbrow bobbrow modified the milestones: 1.11, On Deck Jun 9, 2022
@bobbrow bobbrow changed the title Modify the environment for MSVC Modify the terminal environment for MSVC Aug 23, 2022
@Colengms Colengms removed their assignment Apr 6, 2023
@github-project-automation github-project-automation bot moved this to Triage in On Deck Aug 27, 2024
@bobbrow bobbrow removed this from On Deck Sep 17, 2024
@bobbrow bobbrow assigned bobbrow and unassigned fearthecowboy Jan 7, 2025
@bobbrow bobbrow mentioned this issue Feb 20, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bobbrow bobbrow

Labels
Feature: Configuration An issue related to configuring the extension or IntelliSense Feature Request help wanted Can be fixed in the public (open source) repo. Language Service tasks/build/debug An issue relating to tasks.json (e.g. build issues) Visual Studio Code Caused by (or depends on changes from) VS Code
Projects
None yet
Milestone
On Deck
Development

No branches or pull requests
7 participants
@fearthecowboy @SuperWig @bobbrow @sean-mcmanus @xq114 @jureid @Colengms