From 45e76d7e1abd53721a3236deaff2332832b9b616 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Sat, 1 Nov 2025 02:16:40 +0000
Subject: [PATCH 1/6] Initial plan
From 2c1e34fb1be56b5160015e4b9652c341ec792f2b Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Sat, 1 Nov 2025 02:22:15 +0000
Subject: [PATCH 2/6] Add performance and compatibility info to
EtwManifestEventFormat and EtwSelfDescribingEventFormat docs
Co-authored-by: jkotas <6668460+jkotas@users.noreply.github.com>
---
xml/System.Diagnostics.Tracing/EventSourceSettings.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/xml/System.Diagnostics.Tracing/EventSourceSettings.xml b/xml/System.Diagnostics.Tracing/EventSourceSettings.xml
index 4a78df08fae..b420984ecab 100644
--- a/xml/System.Diagnostics.Tracing/EventSourceSettings.xml
+++ b/xml/System.Diagnostics.Tracing/EventSourceSettings.xml
@@ -137,7 +137,7 @@
4
- The ETW listener should use a manifest-based format when raising events. Setting this option is a directive to the ETW listener should use manifest-based format when raising events. This is the default option when defining a type derived from using one of the protected constructors.
+ The ETW listener should use a manifest-based format when raising events. Setting this option is a directive to the ETW listener should use manifest-based format when raising events. This is the default option when defining a type derived from using one of the protected constructors. This format has lower per-event serialization overhead compared to .
@@ -177,7 +177,7 @@
8
- The ETW listener should use self-describing event format. This is the default option when creating a new instance of the using one of the public constructors.
+ The ETW listener should use self-describing event format. This is the default option when creating a new instance of the using one of the public constructors. This format has more capabilities and better compatibility with ETW profilers that don't use the TraceEvent library, but has higher per-event serialization overhead compared to .
From d93a5ed382d77b6c6143b2bdb2b0c2581aa89719 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Sat, 1 Nov 2025 02:24:44 +0000
Subject: [PATCH 3/6] Remove redundant text from EtwManifestEventFormat
documentation
Co-authored-by: jkotas <6668460+jkotas@users.noreply.github.com>
---
xml/System.Diagnostics.Tracing/EventSourceSettings.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xml/System.Diagnostics.Tracing/EventSourceSettings.xml b/xml/System.Diagnostics.Tracing/EventSourceSettings.xml
index b420984ecab..5f9acd7510a 100644
--- a/xml/System.Diagnostics.Tracing/EventSourceSettings.xml
+++ b/xml/System.Diagnostics.Tracing/EventSourceSettings.xml
@@ -137,7 +137,7 @@
4
- The ETW listener should use a manifest-based format when raising events. Setting this option is a directive to the ETW listener should use manifest-based format when raising events. This is the default option when defining a type derived from using one of the protected constructors. This format has lower per-event serialization overhead compared to .
+ The ETW listener should use a manifest-based format when raising events. This is the default option when defining a type derived from using one of the protected constructors. This format has lower per-event serialization overhead compared to .
From 0586d3a8916b8619157b527883b1a6bdc30713c0 Mon Sep 17 00:00:00 2001
From: Jan Kotas
Date: Fri, 31 Oct 2025 19:34:05 -0700
Subject: [PATCH 4/6] Update
xml/System.Diagnostics.Tracing/EventSourceSettings.xml
---
xml/System.Diagnostics.Tracing/EventSourceSettings.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xml/System.Diagnostics.Tracing/EventSourceSettings.xml b/xml/System.Diagnostics.Tracing/EventSourceSettings.xml
index 5f9acd7510a..c9cc7fe5c03 100644
--- a/xml/System.Diagnostics.Tracing/EventSourceSettings.xml
+++ b/xml/System.Diagnostics.Tracing/EventSourceSettings.xml
@@ -177,7 +177,7 @@
8
- The ETW listener should use self-describing event format. This is the default option when creating a new instance of the using one of the public constructors. This format has more capabilities and better compatibility with ETW profilers that don't use the TraceEvent library, but has higher per-event serialization overhead compared to .
+ The ETW listener should use self-describing event format. This is the default option when creating a new instance of the using one of the public constructors. This format has more capabilities and better compatibility with listeners that don't use the TraceEvent library, but has higher per-event serialization overhead compared to .
From a88d09b14de82b7c44f16c17e94cf2178c7a9e9f Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Sat, 1 Nov 2025 02:37:09 +0000
Subject: [PATCH 5/6] Add link to EventSource documentation for both enum
values
Co-authored-by: jkotas <6668460+jkotas@users.noreply.github.com>
---
xml/System.Diagnostics.Tracing/EventSourceSettings.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/xml/System.Diagnostics.Tracing/EventSourceSettings.xml b/xml/System.Diagnostics.Tracing/EventSourceSettings.xml
index c9cc7fe5c03..728d53ff248 100644
--- a/xml/System.Diagnostics.Tracing/EventSourceSettings.xml
+++ b/xml/System.Diagnostics.Tracing/EventSourceSettings.xml
@@ -137,7 +137,7 @@
4
- The ETW listener should use a manifest-based format when raising events. This is the default option when defining a type derived from using one of the protected constructors. This format has lower per-event serialization overhead compared to .
+ The ETW listener should use a manifest-based format when raising events. This is the default option when defining a type derived from using one of the protected constructors. This format has lower per-event serialization overhead compared to . For more information, see Self-describing (TraceLogging) vs. manifest event formats.
@@ -177,7 +177,7 @@
8
- The ETW listener should use self-describing event format. This is the default option when creating a new instance of the using one of the public constructors. This format has more capabilities and better compatibility with listeners that don't use the TraceEvent library, but has higher per-event serialization overhead compared to .
+ The ETW listener should use self-describing event format. This is the default option when creating a new instance of the using one of the public constructors. This format has more capabilities and better compatibility with listeners that don't use the TraceEvent library, but has higher per-event serialization overhead compared to . For more information, see Self-describing (TraceLogging) vs. manifest event formats.
From baa81b9884287214bd04c463478bd1bc5b516239 Mon Sep 17 00:00:00 2001
From: Jan Kotas
Date: Fri, 31 Oct 2025 19:50:20 -0700
Subject: [PATCH 6/6] Apply suggestions from code review
---
xml/System.Diagnostics.Tracing/EventSourceSettings.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/xml/System.Diagnostics.Tracing/EventSourceSettings.xml b/xml/System.Diagnostics.Tracing/EventSourceSettings.xml
index 728d53ff248..5b2f4ec3dcf 100644
--- a/xml/System.Diagnostics.Tracing/EventSourceSettings.xml
+++ b/xml/System.Diagnostics.Tracing/EventSourceSettings.xml
@@ -137,7 +137,7 @@
4
- The ETW listener should use a manifest-based format when raising events. This is the default option when defining a type derived from using one of the protected constructors. This format has lower per-event serialization overhead compared to . For more information, see Self-describing (TraceLogging) vs. manifest event formats.
+ The ETW listener should use a manifest-based format when raising events. This is the default option when defining a type derived from using one of the protected constructors. This format has lower per-event serialization overhead compared to . For more information, see Self-describing vs. manifest event formats.
@@ -177,7 +177,7 @@
8
- The ETW listener should use self-describing event format. This is the default option when creating a new instance of the using one of the public constructors. This format has more capabilities and better compatibility with listeners that don't use the TraceEvent library, but has higher per-event serialization overhead compared to . For more information, see Self-describing (TraceLogging) vs. manifest event formats.
+ The ETW listener should use self-describing event format. This is the default option when creating a new instance of the using one of the public constructors. This format has more capabilities and better compatibility with listeners that don't use the TraceEvent library, but has higher per-event serialization overhead compared to . For more information, see Self-describing vs. manifest event formats.