.net8 preview4 AOT windows service process, log component always writes to ETW

[xljiulang]

Description

 var builder = WebApplication.CreateSlimBuilder(args);

 builder.Logging.ClearProviders();
 if (ServiceUtil.IsWindowsService() == false)
 {
 builder.Logging.AddConsole();
 }

If the above code is installed and run as a windows service after AOT, the log will always be written to ETW, but the JIT compilation behaves correctly.

Reproduction Steps

1. clear all loger providers.
2. build as AOT
3. install and run as windows service

Expected behavior

Logs are not written to ETW

Actual behavior

Logs allway written to ETW

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

[tommcdon]

@LakshanF do we plan on doing the work in Native AOT to support ETW?

[tommcdon]

@LakshanF would you mind taking a look?

[LakshanF]

@xljiulang, would you be able to give more details of this issue please? We made some recent changes and I would like to understand the impact on your application.

• ETW Provider is opt-in for NativeAOT, similar to the EventPipe provider. PR Make firing of ETW events in nativeaot opt-in via the enabled/disabled lib #88800 made this change. in .NET Applications, both providers are already opted in.
• Setting the EventSourceSupport property to true in your application project file will make both providers (ETW and EventPipe) opted in for your application.
• Not all events are enabled in the ETWProvider for NativeAOT.

Knowing your scenario in detail - ETW events that are important to your application, detailed instructions for the repro of your application - will help us triage this issue for .NET8 release.

Thanks!

This issue has been marked needs-author-action and may be missing some important information.

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Description

 var builder = WebApplication.CreateSlimBuilder(args);

 builder.Logging.ClearProviders();
 if (ServiceUtil.IsWindowsService() == false)
 {
 builder.Logging.AddConsole();
 }

If the above code is installed and run as a windows service after AOT, the log will always be written to ETW, but the JIT compilation behaves correctly.

Reproduction Steps

1. clear all loger providers.
2. build as AOT
3. install and run as windows service

Expected behavior

Logs are not written to ETW

Actual behavior

Logs allway written to ETW

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

Author:	xljiulang
Assignees:	LakshanF
Labels:	area-NativeAOT-coreclr, needs-author-action
Milestone:	8.0.0