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.

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:

• if I set the verbosity to normal, I find that the console output is usually too verbose.
  • but if I set it to minimal then it is not enough...
  • I think that non important messages (Importance below high) are the reason for this/
  • this is probably more due to the lack of colouring of the output.
• when the build fails then I don't have enough information to see what happened. I then set the verbosity to diagnostics but:
  • this is far worse than before on the Console output (obviously).
  • the build takes ages (16' instead of 3' in my current case), probably due to the display on the Console.

I see 2 possibilities to solve this:

• the MSBuild logger could be maybe set to have different verbosity levels : 1 for the Console and 1 for the downloadable log.
  • this is the setup I have for my local builds: normal on the console, diagnostics in a file.
• I could generate myself a detailed log file as part of the build and then upload it to AppVeyor.
  • artifacts cannot be used for this because they are only uploaded if the build succeeds...

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?
Or maybe there are other possibilities.

Best regards.