Repository navigation
DXSharp 0.4.0-preview.3
Pre-releaseDXSharp 0.4.0-preview.3
This preview adds .NET 10 and .NET 11 package assets, refreshed native D3D12 declarations, bounded descriptor pools and upload rings, and stronger command recording ownership.
Runtime and packages
The five modern packages are DXSharp.Native, DXSharp.Core, DXSharp.Assets, DXSharp.DirectML, and DXSharp.Framework.Desktop. Graphics packages target net10.0-windows10.0.26100.0 and net11.0-windows10.0.26100.0; Assets targets net10.0 and net11.0. Windows graphics qualification remains x64.
Samples default to .NET 10. Select .NET 11 with -p:DXSharpRuntimeMajor=11. Building the checkout uses SDK 11.0.100; applications consuming the .NET 10 assets can continue targeting .NET 10.
The dependency pins are Agility 1.620.2, DXC 1.9.2609.5, optional DirectML 1.15.4, Win32Metadata 71.0.45-preview, and CsWin32 0.3.371. Generator dependencies remain private build dependencies.
Native surface and compatibility
The selected D3D12 reference accounts for 752/752 top-level type names and 4,882/4,882 measured member names, resolving the preceding audit's 107 missing D3D12 names. Coverage now compares interface identifiers and fails missing required references or overlapping metadata providers.
This is a preview API compatibility change: older shared shader-cache declarations and associated generated helpers, and SC_HANDLE helpers, are absent from the selected metadata projection. Consumers using them must review the coverage and migration notes. This does not establish that the corresponding native Windows APIs were removed.
Name and IID coverage are not complete ABI verification. Comprehensive signature, inheritance/vtable, and layout verification remains open.
Recording ownership
Command allocators reserve one active recording list. Creating a second recording list against the same allocator, resetting an allocator during recording, and resetting an open list now fail deterministically in managed code. Failed native create/reset calls roll back the reservation. Closing or disposing a recording releases it; pending GPU submissions still prevent unsafe reuse.
A disposed command list releases its native list before its retained recording dependencies. Applications remain responsible for synchronization, resource states, and declaring dependencies used by native recording callbacks.
Descriptor and upload allocation
DescriptorPool reserves contiguous ranges in one native heap; UploadRing reserves aligned slices in one upload buffer. Both expose explicit nonblocking exhaustion and retain each range independently for every recording/submission using it. Owner disposal, timeout, and the completion of only one consuming queue do not reclaim a busy range. Pool disposal stops new allocations while preserving existing allocations and GPU uses.
Managed writes reject recorded or submitted allocations. SRV writes retain their resource dependencies. Allocation-aware descriptor table binding and native recording are available, and RGBA8 texture uploads can share both pools. HelloTexture demonstrates two textures in one descriptor heap. The fixtures compare 20,000 allocation operations against an independent bitmap and verify actual WARP readbacks across two independently blocked queues.
A recording is submitted once. Reset a retired command list before another submission: its allocation ranges may already have been reclaimed. See resource allocation for the complete ownership and no-overwrite contract. Native descriptor writes remain the caller's responsibility; allocation lifetime tracking does not insert resource barriers or cross-queue waits.
Qualification and scope
The merged baseline passed Windows Debug/Release and .NET 10/11 native COM JIT/NativeAOT qualification on Windows and Linux. Native fixtures passed 2,298 checks with zero live objects. Both runtime paths passed package-consumer builds, all 12 package-based sample builds, and Windows WARP sample/lifecycle checks.
The release workflow requalifies the exact release commit and verifies the staged packages before publication. Linux evidence covers the portable COM fixture, not a Linux DirectX renderer. Additional hardware/vendor coverage and production resilience remain open.
Readback rings, placed-resource allocation, general texture formats/mips, GPU-side queue handoff helpers, DirectStorage, current GameInput qualification, and Media Foundation/D3D12 video integration remain follow-up work. No proprietary Noesis dependency is introduced. See the support matrix and parity roadmap.
All repository NativeAOT restores use RID/runtime-specific lock files under artifacts/aot-locks, applied after sample/project properties. A release regression gate exercises fixture AOT, standalone sample AOT, and subsequent locked JIT restores on both runtimes and verifies that canonical lock files remain byte-identical.
NuGet.org accepted the five packages and their symbols from this publishing run. Feed indexing and symbol validation may take additional time.