Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[LiveLogger] Use ProjectConfigurationDescription #8651

Open
Tracked by #8370
ladipro opened this issue Apr 11, 2023 · 1 comment
Open
Tracked by #8370

[LiveLogger] Use ProjectConfigurationDescription #8651

ladipro opened this issue Apr 11, 2023 · 1 comment
Labels
Area: Terminal Logger Problems with the livelogger/fancylogger/terminallogger -tl functionality. triaged

Comments

@ladipro
Copy link
Member

ladipro commented Apr 11, 2023

We should configure using ProjectConfigurationDescription instead, but it's a bit chatty--maybe only the values on the right-hand side?

Originally posted by @rainersigwald in #8619 (comment)

@ladipro ladipro added the Area: Terminal Logger Problems with the livelogger/fancylogger/terminallogger -tl functionality. label Apr 11, 2023
@ladipro ladipro mentioned this issue Apr 11, 2023
@rainersigwald
Copy link
Member

By "right-hand side" I mean that the typical disambiguator from the .NET SDK is something like

TargetFramework=net7.0

Which is a lot of characters and not too interesting. I think the same thing but dropping any TargetFramework= might be good, or we could drop the before-the-equals on every copy of the item to produce strings like net8.0;Value2;Value3 from ProjectConfigurationDescription that has

  • TargetFramework=net8.0
  • Qualifier2=Value2
  • Qualifier3=Value3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Terminal Logger Problems with the livelogger/fancylogger/terminallogger -tl functionality. triaged
Projects
None yet
Development

No branches or pull requests

3 participants