Fix invalid Build command#24771
Conversation
build.cmd does not directly take MSBuild parameters (only after `-MSBuildArguments`) But for configuration, there is already the `-Configuration` parameter.
dougbu
left a comment
There was a problem hiding this comment.
The command documented isn't "invalid" because -MSBuildArguments isn't required. Note the [Parameter(ValueFromRemainingArguments = $true)] on that parameter. But, I agree -Configuration Release works much better than /p:Configuration=Release because -Configuration has a default and unconditionally adds /p:Configuration={default} to the end of the command line.
|
@Tratcher a couple of tests failed in first validation run for this doc-only PR. Suggest they be quarantined:
|
|
Hello @dougbu! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
|
I'm working on PING_NoKeepAliveTimeout_DoesNotResetKeepAliveTimeout. #24797 |
I'm afraid, I don't understand what you are trying to tell. |
|
@softworkz I was simultaneously agreeing and disagreeing with you. |
OK, let's agree to that. It's actually hard to find any tag or branch that builds without issues. Not even the release/3.1 branch. Would you mind taking a look at my recent bug report? #24729 (just in case it's of your concern) Thanks a lot, |
build.cmd does not directly take MSBuild parameters (only after
-MSBuildArguments)But for configuration, there is already the
-Configurationparameter.