Skip to content
This repository was archived by the owner on Jan 31, 2023. It is now read-only.

Conversation

@johnstevenson
Copy link
Contributor

If a source directory is found in the User profile (via
%USERPROFILE%\Source) the VS 2017 Command Prompt script will change to
this directory in its clean-up routines.

This fix uses the VSCMD_START_DIR variable which is provided as an
escape-hatch for this behavior, in ..\core\vsdevcmd_end.bat.

If a `source` directory is found in the User profile (via
%USERPROFILE%\Source) the VS 2017 Command Prompt script will change to
this directory in its clean-up routines.

This fix uses the VSCMD_START_DIR variable which is provided as an
escape-hatch for this behavior, in `..\core\vsdevcmd_end.bat`.
@johnstevenson
Copy link
Contributor Author

I got caught with this because after a new install of VS 2017 Community (v15.4.3) I ended up with a %USERPROFILE%\source folder being created.

More info here: https://developercommunity.visualstudio.com/content/problem/26780/vsdevcmdbat-changes-the-current-working-directory.html

@weltling
Copy link
Member

Merged as 76ed6e3. Many thanks!

@weltling weltling closed this Nov 14, 2017
@johnstevenson johnstevenson deleted the start-dir branch January 29, 2018 12:17
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants