Add comment on native asset linking for WASM PDF rendering

Added documentation in the project file explaining the need to statically link SkiaSharp and HarfBuzzSharp native assets for DevExpress PDF SkiaRenderer support in WASM. Included guidance on the "wasm-tools" workload and the <WasmBuildNative> property. No functional changes made.
This commit is contained in:
2026-05-13 18:44:32 +02:00
parent fe219f58c2
commit e40cd56590

View File

@@ -1,4 +1,4 @@
<Project Sdk="Microsoft.NET.Sdk.BlazorWebAssembly">
<Project Sdk="Microsoft.NET.Sdk.BlazorWebAssembly">
<PropertyGroup>
<TargetFramework>net8.0</TargetFramework>
<Nullable>enable</Nullable>
@@ -6,6 +6,12 @@
<NoDefaultLaunchSettingsFile>true</NoDefaultLaunchSettingsFile>
<StaticWebAssetProjectMode>Default</StaticWebAssetProjectMode>
<MSBuildWarningsAsMessages>$(MSBuildWarningsAsMessage);WASM0001</MSBuildWarningsAsMessages>
<!-- Required so that native assets (libSkiaSharp, libHarfBuzzSharp) from
SkiaSharp.NativeAssets.WebAssembly / HarfBuzzSharp.NativeAssets.WebAssembly
are statically linked into the WASM runtime. Without this the
DevExpress PDF SkiaRenderer throws DllNotFoundException: libSkiaSharp.
Requires the "wasm-tools" workload: dotnet workload install wasm-tools -->
<!--<WasmBuildNative>false</WasmBuildNative>-->
</PropertyGroup>
<ItemGroup>