WebGPU device and presentation
GPU Backend
A thin, explicit foundation between .NET applications and WebGPU.
Explore source ↗Capability
The backend owns adapter and device creation, surfaces, swapchains, command submission, resources, synchronization, and cross-platform window presentation.
- 01
WebGPU adapter and device
- 02
Surfaces and frame presentation
- 03
Explicit GPU resource lifetime
- 04
Cross-platform Silk.NET foundation
How it composes
From intent
to working system.
Adapter
Capability discovery selects a suitable physical backend.
Device
Resources, queues, pipelines, and commands share an owned lifetime.
Surface
Native windows provide presentation targets.
Frame
Applications encode, submit, and present work explicitly.
Quick start
Adopt this
capability.
Start with the primary module, then add the related packages only when the application needs those layers. Replace VERSION with the current NuGet version.
dotnet add package ProGPU.Backend --prerelease<PackageReference Include="ProGPU.Backend" Version="VERSION" /><PackageVersion Include="ProGPU.Backend" Version="VERSION" />await using var backend = await GpuBackend.CreateAsync();using var frame = backend.BeginFrame(surface);
frame.CommandEncoder.Clear(frame.ColorTarget, clearColor);frame.Present();Modules in this capability
Use one layer.
Compose the rest.
Source of truth
Read the module beside the complete system.
The implementation, samples, issues, and release notes stay in the parent repository so module details remain connected to the product architecture.