This repository has been archived by the owner on Feb 19, 2019. It is now read-only.
Generate _env.cmd file instead of bat file for consistency. #469
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Supercedes #468 |
ferventcoder
added a commit
that referenced
this pull request
May 6, 2014
Generate _env.cmd file instead of bat file for consistency.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The RefreshEnv.cmd script generates a _env.bat file. I changed the script to generate a cmd file for consistency.
I was lead to make this change because I found that some organizations use group policy to block the execution of bat files in %TEMP%, but do not block the execution of cmd files. This might just be an oversight in the group policy configuration, but I figure it wouldn't hurt to use the newer "cmd" convention, especially if it isn't blocked.