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

Serilog does not log to file in WinUI #2491

Open
1 of 10 tasks
frogcrush opened this issue Aug 1, 2024 · 0 comments · May be fixed by #2492
Open
1 of 10 tasks

Serilog does not log to file in WinUI #2491

frogcrush opened this issue Aug 1, 2024 · 0 comments · May be fixed by #2492
Labels
kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification.

Comments

@frogcrush
Copy link

Current behavior

Using UseSerilog(fileLoggingEnabled: true) has no effect on a WinUI app.

Expected behavior

Log files should be generated in the app folder.

How to reproduce it (as minimally and precisely as possible)

  • Create a new WinUI Uno app with Serilog
  • Enable file logging as above
  • See no log file output on Windows

Environment

Nuget Package (s): Uno.Extensions.logging.Serilog

Package Version(s): 4.2.0-dev.81

Affected platform(s):

  • iOS
  • macOS (AppKit)
  • Mac Catalyst
  • Android
  • WebAssembly
  • Windows
  • Skia (WPF)
  • Skia (GTK on Linux/macOS/Windows)
  • Skia (Linux Framebuffer)
  • Build tasks

Anything else we need to know?

Looking at the code it checks for #if NETSTANDARD which might not apply in WinUI but would have in UWP?

@frogcrush frogcrush added kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification. labels Aug 1, 2024
@frogcrush frogcrush linked a pull request Aug 1, 2024 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant