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.

Properties and items aren't logged at evaluation for `dotnet build`

See original GitHub issue

Unlike MSBuild, when you run dotnet build, something is preventing the new behavior of logging properties and items after evaluation.

As a result we get legacy broken behavior where some properties and items are logged for some projects at ProjectStarted, but not others, and none at all are logged at evaluation.

This is very bad and we should fix this soon.

Issue Analytics

State:
Created 2 years ago
Comments:11 (11 by maintainers)

Top GitHub Comments

1reaction

rainersigwaldcommented, Jan 4, 2022

Yup, that’s what I see with my private build:

0reactions

KirillOsenkovcommented, Jan 4, 2022

https://github.com/dotnet/msbuild/pull/7217

Top Results From Across the Web

Logging in .NET Core and ASP.NET Core

Logging providers; Create logs; Configure logging; Log in Program.cs ... The Logging property can have LogLevel and log provider properties.

How to pass build properties to dotnet?

the dotnet build command accepts MSBuild options, such as /p for setting properties or /l to define a logger.

Is there a .Net attribute to prevent property evaluation ...

I have experience with the Debugger Browsable attribute; however, I would prefer to display the properties after the main thread has accessed / ......

Where are .NET Errors Logged?

This simple guide explains where .NET logs are located, how to configure logging, and why error monitoring tools like Rollbar make debugging ...

.NET Logging: Best Practices for your .NET Application ...

Learn more about .NET logging and the best practices for your .NET application with this comprehensive guide.