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"