Bug 43990 - verbosity minimal should show target name
Summary: verbosity minimal should show target name
Status: RESOLVED NOT_ON_ROADMAP
Alias: None
Product: Tools
Classification: Mono
Component: xbuild ()
Version: 4.2.1 (C6SR0)
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-09-04 15:38 UTC by Chris Capon
Modified: 2018-03-15 10:39 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NOT_ON_ROADMAP

Description Chris Capon 2016-09-04 15:38:52 UTC
When verbosity minimal is selected, the output shows configuration information, warnings and errors.

The output for solutions with multiple projects can become confusing as the project name are not shown.  There is no easy way to know which project a warning or error message belongs to without raising the verbosity level.

Here is a sample output from a multi-project solution.  Notice the name of the project which caused the warning message is absent.

----------------------------

xbuild  "code/lib/lib.sln"  /target:Build  /verbosity:normal  /toolsversion:4.0  "/property:TargetFrameworkVersion=v4.5.1;Configuration=Release;Platform=Any CPU"  /nologo


Configuration: Release Platform: AnyCPU
Configuration: Release Platform: AnyCPU
Configuration: Release Platform: AnyCPU
Configuration: Release Platform: AnyCPU
Configuration: Release Platform: AnyCPU
Configuration: Release Platform: AnyCPU
Configuration: Release Platform: AnyCPU
/usr/lib/mono/4.5/Microsoft.Common.targets:  warning : TargetFrameworkVersion 'v4.5.1' not supported by this toolset (ToolsVersion: 4.0).
Configuration: Release Platform: AnyCPU
Configuration: Release Platform: AnyCPU
Configuration: Release Platform: AnyCPU
Configuration: Release Platform: AnyCPU
Configuration: Release Platform: AnyCPU
Configuration: Release Platform: AnyCPU
Configuration: Release Platform: AnyCPU
Configuration: Release Platform: AnyCPU
Configuration: Release Platform: AnyCPU
/usr/lib/mono/4.5/Microsoft.Common.targets:  warning : TargetFrameworkVersion 'v4.5.1' not supported by this toolset (ToolsVersion: 4.0).

---------------------------

I think showing the project name is more important than seeing its configuration.
Thanks.
Comment 1 Alex Earl 2016-12-13 17:54:02 UTC
msbuild's minimal output looks similar to this:

---------------------------
  Microsoft.Scripting -> C:\code\_external\ironpython3\Src\DLR\bin\Debug\Microsoft.Scripting.dll
  Microsoft.Scripting.Metadata -> C:\code\_external\ironpython3\Src\DLR\bin\Debug\Microsoft.Scripting.Metadata.dll
  Microsoft.Dynamic -> C:\code\_external\ironpython3\Src\DLR\bin\Debug\Microsoft.Dynamic.dll
  IronPython -> C:\code\_external\ironpython3\bin\Debug\IronPython.dll
  IronPython.Modules -> C:\code\_external\ironpython3\bin\Debug\IronPython.Modules.dll
  IronPython.Wpf -> C:\code\_external\ironpython3\bin\Debug\DLLs\IronPython.Wpf.dll
  IronPythonConsole -> C:\code\_external\ironpython3\bin\Debug\ipy.exe
  IronPythonTest -> C:\code\_external\ironpython3\bin\Debug\IronPythonTest.exe
  IronPythonWindow -> C:\code\_external\ironpython3\bin\Debug\ipyw.exe
  IronPythonConsoleAny -> C:\code\_external\ironpython3\bin\Debug\ipy64.exe
  IronPythonWindowAny -> C:\code\_external\ironpython3\bin\Debug\ipyw64.exe
  IronPython.SQLite -> C:\code\_external\ironpython3\bin\Debug\DLLs\IronPython.SQLite.dll
  IronPythonCompiler -> C:\code\_external\ironpython3\bin\Debug\ipyc.exe
  Microsoft.Scripting -> C:\code\_external\ironpython3\Src\DLR\bin\v45Debug\Microsoft.Scripting.dll
  Microsoft.Scripting.Metadata -> C:\code\_external\ironpython3\Src\DLR\bin\v45Debug\Microsoft.Scripting.Metadata.dll
  Microsoft.Dynamic -> C:\code\_external\ironpython3\Src\DLR\bin\v45Debug\Microsoft.Dynamic.dll
  IronPython -> C:\code\_external\ironpython3\bin\v45Debug\IronPython.dll
  IronPython.Modules -> C:\code\_external\ironpython3\bin\v45Debug\IronPython.Modules.dll
  IronPython.Wpf -> C:\code\_external\ironpython3\bin\v45Debug\DLLs\IronPython.Wpf.dll
  IronPythonConsole -> C:\code\_external\ironpython3\bin\v45Debug\ipy.exe
  IronPythonTest -> C:\code\_external\ironpython3\bin\v45Debug\IronPythonTest.exe
  IronPythonWindow -> C:\code\_external\ironpython3\bin\v45Debug\ipyw.exe
  IronPythonConsoleAny -> C:\code\_external\ironpython3\bin\v45Debug\ipy64.exe
  IronPythonWindowAny -> C:\code\_external\ironpython3\bin\v45Debug\ipyw64.exe
  IronPython.SQLite -> C:\code\_external\ironpython3\bin\v45Debug\DLLs\IronPython.SQLite.dll
  IronPythonCompiler -> C:\code\_external\ironpython3\bin\v45Debug\ipyc.exe
-----------------------------
Comment 2 Alex Earl 2017-03-06 16:20:45 UTC
I'm pretty sure this is happening because of the .targets files that mono currently has. They are not the same as the ones from MS.NET and the configuration information is coming from there. I also looked at the MS.NET ones and that is where the output I showed is from.
Comment 3 Chris Capon 2017-03-06 17:05:12 UTC
Running the same solution file through MSBuild produces the text below (so it matches what you are seeing too).  It looks like the target name followed by the resulting output file.

If we could have this added to xbuild then the additional information about Configuration and Platform could stay.  That way we don't have to count down and guess which project has a warning or error.

Much Thanks. :-)


C:\Users\cc\xx\Dev>"C:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe" "code/lib/lib.sln" /target:Build /verbosity:minimal
Microsoft (R) Build Engine version 14.0.25420.1
Copyright (C) Microsoft Corporation. All rights reserved.

  lib.support -> C:\Users\cc\xx\Dev\code\lib\support\lib.support.dll
  lib.xml -> C:\Users\cc\xx\Dev\code\lib\xml\lib.xml.dll
  lib.work -> C:\Users\cc\xx\Dev\code\lib\work\lib.work.dll
  Xslt -> C:\Users\cc\xx\Dev\code\tools\Xslt\Xslt.exe
  Transformer -> C:\Users\cc\xx\Dev\code\tools\Transformer\Transformer.exe
  lib.data -> C:\Users\cc\xx\Dev\code\lib\data\lib.data.dll
  lib.Audit -> C:\Users\cc\xx\Dev\code\lib\Audit\lib.Audit.dll
  lib.Excel -> C:\Users\cc\xx\Dev\code\lib\Excel\lib.Excel.dll
  lib.Grid -> C:\Users\cc\xx\Dev\code\lib\Grid\lib.Grid.dll
  lib.DataSetSerialize -> C:\Users\cc\xx\Dev\code\lib\DataSetSerialize\lib.DataSetSerialize.dll
  lib.ini -> C:\Users\cc\xx\Dev\code\lib\ini\lib.ini.dll
  lib.ZipPackages -> C:\Users\cc\xx\Dev\code\lib\ZipPackages\lib.ZipPackages.dll
  lib.testing -> C:\Users\cc\xx\Dev\code\lib\testing\lib.testing.dll
  lib.database -> C:\Users\cc\xx\Dev\code\lib\database\lib.database.dll
  lib.rest -> C:\Users\cc\xx\Dev\code\lib\rest\lib.rest.dll
  lib._Testing -> C:\Users\cc\xx\Dev\code\lib\_Testing\lib._Testing.dll

C:\Users\cc\xx\Dev>
Comment 4 Marek Safar 2018-03-15 10:39:58 UTC
We deprecated xbuild and recommend using msbuild instead. Switching to msbuild will also most likely resolve the issue you reported.