tag:help.appveyor.com,2012-11-13:/discussions/questions/40078-msbuild-logger-verbosityAppVeyor: Discussion 2019-08-05T09:55:53Ztag:help.appveyor.com,2012-11-13:Comment/474939922019-08-02T09:44:36Z2019-08-02T09:44:36ZMSBuild logger verbosity<div><p>I am in the process of integrating a .NET Core 3.0 preview 7 project in AppVeyor. Living on the edge as I am, I regularly run into build problems: lots of things have changed since the .NET Framework, and sometimes I run into issues due to the young age of this platfom.</p>
<p>My trouble there lies with the verbosity of the MSBuild logger. I realize I had the same problem with the regular .NET Framework, but it is more acute now due to the reasons above:</p>
<ul>
<li>if I set the verbosity to <em>normal</em>, I find that the console output is usually too verbose.
<ul>
<li>but if I set it to <em>minimal</em> then it is not enough...</li>
<li>I think that non important messages (<a href="https://docs.microsoft.com/en-us/visualstudio/msbuild/message-task?view=vs-2019">Importance below <em>high</em></a>) are the reason for this/</li>
<li>this is probably more due to the lack of colouring of the output.</li>
</ul>
</li>
<li>when the build fails then I don't have enough information to see what happened. I then set the verbosity to <em>diagnostics</em> but:
<ul>
<li>this is far worse than before on the Console output (obviously).</li>
<li>the build takes ages (16' instead of 3' in my current case), probably due to the display on the Console.</li>
</ul>
</li>
</ul>
<p>I see 2 possibilities to solve this:</p>
<ul>
<li>the MSBuild logger could be maybe set to have different verbosity levels : 1 for the Console and 1 for the downloadable log.
<ul>
<li>this is the setup I have for my local builds: <em>normal</em> on the console, <em>diagnostics</em> in a file.</li>
</ul>
</li>
<li>I could generate myself a detailed log file as part of the build and then upload it to AppVeyor.
<ul>
<li>artifacts cannot be used for this because they are only uploaded if the build succeeds...</li>
</ul>
</li>
</ul>
<p>I realize that any of these would likely require some development efforts on your part (and probably impacting the whole platform). But do you think these could be considered?<br>
Or maybe there are other possibilities.</p>
<p>Best regards.</p></div>mathieu.cartoixatag:help.appveyor.com,2012-11-13:Comment/474939922019-08-02T16:58:45Z2019-08-02T16:58:45ZMSBuild logger verbosity<div><p>You can upload artifacts with <a href="https://www.appveyor.com/docs/packaging-artifacts/#pushing-artifacts-from-scripts">script</a> at <code>on_failure:</code> section of build config.</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/474939922019-08-05T09:55:52Z2019-08-05T09:55:52ZMSBuild logger verbosity<div><p>Thanks, this definitely will save me time in the meantime.</p></div>mathieu.cartoixa