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.

.NET 5 produces warning in logs

See original GitHub issue

{“Service”} Failed to detect whether the current .NET runtime is .NET Full Framework, Mono or .NET Core - `“N/A”’ will be used as the current .NET runtime name

Issue Analytics

State:
Created 3 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

ffMathycommented, Nov 17, 2020

It worked!

0reactions

russcamcommented, Nov 15, 2020

1.7.0 is now released to nuget, which includes #964

@ffMathy please can you try with 1.7.0 and see if this resolves the issue?

Top Results From Across the Web

Logging in .NET Core and ASP.NET Core

Logging at Warning through Critical levels should produce few log messages. Costs and storage limits usually aren't a concern. Few logs allow ...

The logging message template should not vary between ...

This is actually a relevant warning. When producing logs within your application, you should not include variables to construct your log ...

Where are .NET Errors Logged?

NET Core Logging File, we can log a message, error, or warnings to a text file within three steps; they are as follows....

.NET Logging Basics - The Ultimate Guide To Logging - Loggly

A warning is simply a level for alerting the administrator of a possible problem. Information: Provides details about what's happening behind the scenes...

Don't let ASP.NET Core Console Logging Slow your App down

Luckily the default templates handle setting the Logging Level to Warning in production, but the raw default Logging Level of Information is ...