-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[DOC] Default value of IgnoreStandardErrorWarningFormat inconsistent between product & MSDN #766
Comments
This isn't just an inconsistency, it's a horrible, horrible hack to fail the build due to some "standard error and warning format" messages. This so-called "standard format" isn't even documented on the linked MSDN page and this is certainly unexpected behaviour for someone creating a pre-build or post-build step in Visual Studio. This hack should certainly be off by default, like the documentation says it is and if someone does want to turn it on, they should have documentation on exactly what strings it looks for. Looks like I'm not the only one to run into it: http://stackoverflow.com/questions/39466090/why-outputting-error-in-post-build-event-breaks-my-build-in-vs2012 |
The property also says it defaults to From what I can tell, it's always been |
Thanks for the heads up on this. Looking into it now. |
IgnoreStandardErrorWarningFormat default is false. See: #766
Comment correction. Comment states that _ignoreStandardErrorWarningFormat defaults to true, but it defaults to false. Brought up in discussion #766.
I don't think this closes the issue. We need the docs site updated, too. |
MSDN docs has been updated to correct default value of false. This exact page hasn't been moved over to docs, so I added a line specifying the default value in docs under "IgnoreStandardErrorWarningFormat": https://docs.microsoft.com/en-us/visualstudio/msbuild/exec-task |
According to MSDN,
IgnoreStandardErrorWarningFormat
should default totrue
. This shows that it's false. They should be consistent.The text was updated successfully, but these errors were encountered: