Fixes

Author: aritchie

.github/workflows/deploy-blazor-sample.yml

@@ -42,8 +42,15 @@ jobs:
         with:
           dotnet-version: '10.0.x'
 
+      # wasm-tools has to be named explicitly: `dotnet workload restore` installs nothing for a
+      # Blazor WebAssembly project, and without the workload the SkiaSharp native relink is skipped
+      # silently — the publish succeeds and every Office view then throws
+      # "DllNotFoundException: libSkiaSharp" in the browser. The guard imported by Sample.Blazor.csproj
+      # turns that back into a build failure, but the workload is what actually fixes it.
       - name: Restore workloads
-        run: dotnet workload restore "${{ env.SAMPLE_CSPROJ }}"
+        run: |
+          dotnet workload install wasm-tools
+          dotnet workload restore "${{ env.SAMPLE_CSPROJ }}"
 
       - name: Publish
         run: dotnet publish "${{ env.SAMPLE_CSPROJ }}" -c Release -o publish

README.md

@@ -905,7 +905,9 @@ await workbook.SaveAsync();
 | Reporting | `UnsupportedFeatureCollector` names anything in a document the editor cannot show or edit |
 
 **Constraints.** Blazor is **WebAssembly only** (a Server round-trip per keystroke is unusable, and
-SkiaSharp on WASM needs the `wasm-tools` workload). MAUI requires `UseSkiaSharp()`. Inserting and
+SkiaSharp on WASM needs the `wasm-tools` workload — without it `libSkiaSharp` is never linked into the
+runtime and the app fails in the browser, so `Shiny.Blazor.Controls.Office` fails the build up front
+with `SHINY0001` instead; bypass with `ShinySkipWasmToolsCheck=true`). MAUI requires `UseSkiaSharp()`. Inserting and
 deleting rows and columns is deliberately not implemented — it requires rewriting references across
 formulas, merged cells, conditional formatting, defined names, data validation, charts and tables.
 

samples/Sample.Blazor/Sample.Blazor.csproj

@@ -5,6 +5,11 @@
         <RootNamespace>Sample.Blazor</RootNamespace>
     </PropertyGroup>
 
+    <!-- ProjectReference does not flow a package's buildTransitive targets, so the wasm-tools guard
+         that ships in Shiny.Blazor.Controls.Office is imported by hand here — this sample publishes
+         to GitHub Pages and a missing workload silently ships a broken Office demo. -->
+    <Import Project="..\..\src\Shiny.Blazor.Controls.Office\buildTransitive\Shiny.Blazor.Controls.Office.targets" />
+
     <ItemGroup>
         <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly"/>
         <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly.DevServer" PrivateAssets="all"/>

src/Shiny.Blazor.Controls.Office/Shiny.Blazor.Controls.Office.csproj

@@ -7,6 +7,12 @@
         <Description>Spreadsheet viewer and editor for Blazor WebAssembly, rendering .xlsx on a SkiaSharp canvas.</Description>
     </PropertyGroup>
 
+    <ItemGroup>
+        <!-- Fails the consumer's build when the wasm-tools workload is missing, instead of letting
+             them publish an app that dies on the first Skia call. See the targets file. -->
+        <None Include="buildTransitive/Shiny.Blazor.Controls.Office.targets" Pack="true" PackagePath="buildTransitive/Shiny.Blazor.Controls.Office.targets" />
+    </ItemGroup>
+
     <ItemGroup>
         <SupportedPlatform Include="browser" />
         <PackageReference Include="Microsoft.AspNetCore.Components.Web"/>

src/Shiny.Blazor.Controls.Office/buildTransitive/Shiny.Blazor.Controls.Office.targets

@@ -0,0 +1,17 @@
+<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
+  <!--
+    Every Office view paints through SkiaSharp, and SkiaSharp for WebAssembly ships only a static
+    libSkiaSharp.a. It is linked into the runtime by the native relink step, which runs only when the
+    wasm-tools workload is installed. Without the workload the NativeFileReference is silently
+    dropped: restore, build and publish all succeed, and the first Skia call in the browser throws
+    "DllNotFoundException: libSkiaSharp" with a blank canvas behind it. Fail the build instead.
+  -->
+  <Target
+    Name="_ShinyBlazorControlsOfficeCheckWasmTools"
+    BeforeTargets="PrepareForBuild"
+    Condition="'$(RuntimeIdentifier)' == 'browser-wasm' AND '$(WasmNativeWorkloadAvailable)' != 'true' AND '$(ShinySkipWasmToolsCheck)' != 'true'">
+    <Error
+      Code="SHINY0001"
+      Text="Shiny.Blazor.Controls.Office renders with SkiaSharp, which needs the 'wasm-tools' workload so that libSkiaSharp gets linked into the WebAssembly runtime. Install that workload (`dotnet workload install wasm-tools`) — note that `dotnet workload restore` does NOT pull it in for a Blazor WebAssembly project. Without it the app builds and publishes clean, then fails in the browser with DllNotFoundException: libSkiaSharp. Set ShinySkipWasmToolsCheck=true to bypass this check." />
+  </Target>
+</Project>