From 3c08139d912d65c5d0cd3333cb8b5943ca2cfff5 Mon Sep 17 00:00:00 2001
From: tiger tiger tiger <tiger@tiger.blue>
Date: Mon, 6 Jul 2026 15:41:36 +0200
Subject: [PATCH] fix: let the binding build for browser-wasm on both net8.0
 and net10.0

The net8-era wasm workload (Microsoft.NET.Runtime.WebAssembly.Sdk 8.0.x,
auto-imported for RID browser-wasm) treats every browser-wasm project as
a wasm app: it forces OutputType=Exe after project evaluation (CS5001
for a classlib) and hooks its app-bundle build after Build, which errors
because a library has no assemblies to bundle. Opt Raylib-cs out via
DisableAutoWasmBuildApp (props time, before the workload defaults its
trigger) and pin OutputType back to Library in Directory.Build.targets
(evaluated after the workload props, so the assignment wins). net10's
wasm SDK needs neither workaround.
---
 Directory.Build.props   | 8 ++++++++
 Directory.Build.targets | 9 +++++++++
 2 files changed, 17 insertions(+)

diff --git a/Directory.Build.props b/Directory.Build.props
index 1787477..92fc659 100644
--- a/Directory.Build.props
+++ b/Directory.Build.props
@@ -3,4 +3,12 @@
   <PropertyGroup>
     <RaylibCsVersion>8.1.0</RaylibCsVersion>
   </PropertyGroup>
+
+  <!-- The net8-era wasm workload treats any browser-wasm project as a wasm *app* and hooks
+       its app-bundle build after Build, which fails for a plain classlib. Opt the binding out
+       (must happen at props time, before the workload defaults WasmBuildAppAfterThisTarget).
+       The matching OutputType pin lives in Directory.Build.targets. -->
+  <PropertyGroup Condition="'$(MSBuildProjectName)' == 'Raylib-cs' And '$(RuntimeIdentifier)' == 'browser-wasm'">
+    <DisableAutoWasmBuildApp>true</DisableAutoWasmBuildApp>
+  </PropertyGroup>
 </Project>
diff --git a/Directory.Build.targets b/Directory.Build.targets
index 89f1009..8584d9b 100644
--- a/Directory.Build.targets
+++ b/Directory.Build.targets
@@ -1,4 +1,13 @@
 <Project>
+  <!-- The net8-era wasm workload (Microsoft.NET.Runtime.WebAssembly.Sdk 8.0.x, imported for
+       RID browser-wasm) unconditionally sets OutputType=Exe after project evaluation, which
+       breaks the net8.0 classlib build with CS5001. Pin it back to Library here: this file is
+       imported after the workload props, so the assignment wins. (net10's wasm SDK leaves
+       OutputType alone; Examples stays an Exe and is excluded.) -->
+  <PropertyGroup Condition="'$(MSBuildProjectName)' == 'Raylib-cs' And '$(RuntimeIdentifier)' == 'browser-wasm'">
+    <OutputType>Library</OutputType>
+  </PropertyGroup>
+
   <!-- Raylib-cs 8.1.0 is not on nuget.org yet; pack locally so Examples and tests resolve the package with native runtimes. -->
   <Target Name="_EnsureLocalRaylibCsPackage"
           BeforeTargets="Restore"