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

Removing the "all arguments" argument #116

Merged
merged 1 commit into from
Feb 1, 2012
Merged

Removing the "all arguments" argument #116

merged 1 commit into from
Feb 1, 2012

Conversation

AnthonyMastrean
Copy link
Contributor

I didn't realize the implications of passing "all args" into the next batch file. I thought you could use it from the command line like

cmd> build-Release.bat /p:CustomParam=Whatever

However, in the next batch file, you'd have to do some crazy batch for looping to get the "remaining" arguments. Since, in that batch file, %* would have the %configuration% and everything else in it. Capische?

I didn't realize the implications of passing "all args" into the next batch file. I thought you could use it from the command line like

    cmd> build-Release.bat /p:CustomParam=Whatever

However, in the next batch file, you'd have to do some [crazy batch for looping][1] to get the "remaining" arguments. Since, in that batch file, `%*` would have the `%configuration%` and everything else in it. Capische?

 [1]: http://stackoverflow.com/a/761658/3619
distantcam added a commit that referenced this pull request Feb 1, 2012
Removing the "all arguments" argument
@distantcam distantcam merged commit b7c42dd into Code52:master Feb 1, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants