Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Paket prints too many restore information with `--no-restore` in `dotnet build --no-restore`

See original GitHub issue

Description

Paket prints too many restore information with --no-restore in dotnet build --no-restore This is the case with the latest 5.193.0 The older 5.163.2 works as expected/desired.

Repro steps

Use attached project with latest Paket.5.193.0

Invoke commands:

.paket\paket.exe restore
dotnet restore
dotnet build --no-restore

Expected behavior

Output of the last command dotnet build --no-restore should be:

Microsoft (R) Build Engine version 15.9.20+g88f5fadfbe for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  Test1 -> C:\Users\rjq\Desktop\_181206_105136_pk\Paket.5.193.0\bin\Debug\netstandard2.0\Test1.dll

Build succeeded.
    0 Warning(s)
    0 Error(s)

Actual behavior

Output of the last command dotnet build --no-restore contains too many information about restoring:

Microsoft (R) Build Engine version 15.9.20+g88f5fadfbe for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  Paket version 5.193.0
  The last restore is still up to date. Nothing left to do.
  Performance:
   - Runtime: 128 milliseconds
  Test1 -> C:\Users\rjq\Desktop\_181206_105136_pk\Paket.5.193.0\bin\Debug\netstandard2.0\Test1.dll

Build succeeded.
    0 Warning(s)
    0 Error(s)

The picture is even worse if we build a solution with many projects (30+ in our case). For every project we get 1 useful log line about DLL and 4 noise lines about restoring.