Suppress noisy analyzer rules in benchmarks and examples csproj

benchmarks/Wolfgang.TryPattern.Benchmarks/Wolfgang.TryPattern.Benchmarks.csproj

@@ -5,6 +5,18 @@
     <TargetFramework>net8.0</TargetFramework>
     <ImplicitUsings>enable</ImplicitUsings>
     <Nullable>enable</Nullable>
+
+    <!--
+      Suppress analyzer rules that are noisy or non-applicable in benchmark code.
+      These are firing on the Windows CI runner despite being relaxed in
+      .editorconfig's [benchmarks/**/*.cs] section, so we suppress at the project
+      level for explicit, reliable enforcement.
+    -->
+    <NoWarn>$(NoWarn);
+      MA0004;    <!-- ConfigureAwait - benchmarks intentionally use SynchronizationContext-equivalent default -->
+      VSTHRD200; <!-- Async naming - benchmark methods don't follow 'Async' suffix convention -->
+      S6966      <!-- Sync vs async - benchmarks intentionally compare both -->
+    </NoWarn>
   </PropertyGroup>
 
   <ItemGroup>

examples/CSharp.DotNet8.Example/CSharp.DotNet8.Example.csproj

@@ -5,6 +5,17 @@
     <TargetFramework>net8.0</TargetFramework>
     <ImplicitUsings>enable</ImplicitUsings>
     <Nullable>enable</Nullable>
+
+    <!--
+      Suppress analyzer rules that are noisy or non-applicable in example code.
+      These are firing on the Windows CI runner despite being relaxed in
+      .editorconfig's [examples/**/*.cs] section, so we suppress at the project
+      level for explicit, reliable enforcement.
+    -->
+    <NoWarn>$(NoWarn);
+      MA0004;    <!-- ConfigureAwait - examples are end-user code, ConfigureAwait shouldn't be required -->
+      S6966      <!-- Sync vs async - examples can demonstrate either form -->
+    </NoWarn>
   </PropertyGroup>
 
   <ItemGroup>