UAIX.LmRuntime / Package guide

UAIX.LmRuntime.Backends.DirectML

DirectML backend registration, declared compatibility metadata, runtime identifiers, and fail-closed local probe diagnostics.

Required For DirectML backend registration and fail-closed DirectML diagnostics

UAIX.LmRuntime.Backends.DirectML

DirectML backend registration, declared compatibility metadata, runtime identifiers, and fail-closed local probe diagnostics.

Open on NuGet Package family

Overview

Backends.DirectML registers the UAIX DirectML backend family with Acceleration. It declares the intended DirectML capability surface and package runtime identifiers (win-x64), then probes unavailable until a host-supplied native adapter proves assets, runtime libraries, drivers, and a device. The managed package performs no hidden native inference.

Who should use it Hosts building an explicit DirectML compatibility lane, diagnostics UI, deployment validation, or future native adapter integration for Windows GPU hosts.

Install

.NET CLI

dotnet add package UAIX.LmRuntime.Backends.DirectML

Project file

<PackageReference Include="UAIX.LmRuntime.Backends.DirectML" />

Version policy: The documentation deliberately omits UAIX.LmRuntime package version numbers. Resolve and pin versions through your normal dependency-management and lock-file process.

Review the current package metadata, frameworks, dependencies, and downloads on NuGet ↗

Direct package dependencies

UAIX.LmRuntime.AccelerationNuGet ↗

Package role and boundaries

Required For DirectML backend registration and fail-closed DirectML diagnostics

You need the stable DirectML backend ID and registry extension.
You need package-visible DirectML runtime-identifier and capability declarations.
You need fail-closed probe diagnostics before DirectML execution is proven.

Boundary

Installing or registering this package does not prove DirectML execution.
The supplied managed backend does not load native inference libraries or enumerate a real device.
Do not report GPU availability unless a host adapter returns an available probe with concrete device evidence.

Registration is not execution

AddUaixDirectMlBackend adds metadata and probe behavior to the registry; it does not start a DirectML engine.

Compatibility fails closed

The default diagnostic probe returns unavailable and states which native evidence has not been supplied.

Runtime identifiers are declared

The package declares win-x64; the current process and deployment still require independent validation.

Key types

These are the main entry points for this package. The generated reference below includes every documented type and member represented by public package XML documentation.

DirectMlRuntimeBackend RuntimeBackendRegistryExtensions

Coding examples

Examples use public package signatures documented on LMRuntime.com. Model paths, hashes, byte counts, prompts, and host-specific identifiers remain application inputs.

Register the DirectML backend

Add the package-visible DirectML backend to an explicit Acceleration registry.

RegisterDirectMlExample.cs

using UAIX.LmRuntime.Acceleration;
using UAIX.LmRuntime.Backends.DirectML;

var registry = new RuntimeBackendRegistry();
registry.AddUaixDirectMlBackend();

IRuntimeBackend backend = registry.FindById(DirectMlRuntimeBackend.BackendId)
    ?? throw new InvalidOperationException("DirectML backend registration failed.");

Console.WriteLine($"{backend.Id} / {backend.Kind}");

Boundary: Registration exposes DirectML diagnostics. It does not prove a native runtime or device.

Probe the DirectML package boundary

Inspect declared capabilities and the independent availability result.

ProbeDirectMlExample.cs

using UAIX.LmRuntime.Acceleration;
using UAIX.LmRuntime.Backends.DirectML;

var backend = new DirectMlRuntimeBackend();
RuntimeBackendProbeResult probe = await backend.ProbeAsync(
    new RuntimeBackendOptions
    {
        RequestedRuntimeIdentifier =
            System.Runtime.InteropServices.RuntimeInformation.RuntimeIdentifier,
        RequireNativeAssets = true
    });

Console.WriteLine($"Declared API: {probe.Capabilities.BackendApiName}");
Console.WriteLine($"Native state: {probe.Capabilities.NativeAssetState}");
Console.WriteLine($"Available: {probe.IsAvailable}");
foreach (string diagnostic in probe.Diagnostics)
{
    Console.WriteLine(diagnostic);
}

Boundary: The default probe is expected to remain unavailable until a production adapter proves DirectML assets, runtime libraries, and a device.

Require the DirectML backend by ID

Reject CPU substitution when the workload contract specifically requires DirectML.

RequireDirectMlExample.cs

using UAIX.LmRuntime.Acceleration;
using UAIX.LmRuntime.Backends.DirectML;

var registry = new RuntimeBackendRegistry();
registry.AddUaixDirectMlBackend();

var selector = new RuntimeBackendSelector(registry);
RuntimeSelectionResult result = await selector.SelectAsync(
    new RuntimeBackendOptions
    {
        Policy = RuntimeSelectionPolicy.RequireBackendId,
        PreferredBackendId = DirectMlRuntimeBackend.BackendId,
        AllowCpuFallback = false,
        RequireNativeAssets = true
    });

if (!result.Succeeded)
{
    Console.Error.WriteLine(result.FailureReason);
}

Boundary: RequireBackendId fails instead of relabeling another backend as DirectML.

List the DirectML package runtime identifiers

Use declared identifiers as deployment metadata, not as proof that the current machine is ready.

DirectMlRuntimeIdentifiersExample.cs

using UAIX.LmRuntime.Backends.DirectML;

var backend = new DirectMlRuntimeBackend();
foreach (string runtimeIdentifier in backend.Capabilities.RuntimeIdentifiers)
{
    Console.WriteLine(runtimeIdentifier);
}

Boundary: The declared identifiers are win-x64. Probe evidence remains required for a usable DirectML execution path.

Open this package on NuGet Compare the full package family →

Generated API reference

Expand a type to review its documented fields, properties, constructors, methods, parameter descriptions, and return descriptions. Browser Find also works across the closed detail elements.

DirectMlRuntimeBackendUAIX.LmRuntime.Backends.DirectML 2 members

Reports DirectML backend compatibility and diagnostics to the acceleration registry.

DirectML support is declared as a package-visible compatibility path for Windows hosts. This package performs no hidden native inference and reports unavailable until a host supplies native runtime and device evidence.

Field BackendId

The stable backend identifier used by selection policies.

Method DirectMlRuntimeBackend

Initializes a new instance of the UAIX.LmRuntime.Backends.DirectML.DirectMlRuntimeBackend class.

RuntimeBackendRegistryExtensionsUAIX.LmRuntime.Backends.DirectML 1 member

Provides registration helpers for the DirectML backend.

Registration only exposes diagnostics and selection metadata. It does not authorize hidden native execution.

Method AddUaixDirectMlBackend(UAIX.LmRuntime.Acceleration.IRuntimeBackendRegistry)

Adds the UAIX DirectML backend to a registry.

registry: The registry to update.

Returns: The same registry instance for fluent configuration.

Frequently asked questions

Does this package execute through DirectML today?

The managed registration package reports unavailable until a host-supplied native adapter proves DirectML assets, runtime libraries, drivers, and a device.

Why does SupportsGpuExecution read true when IsAvailable is false?

Capabilities describe the backend family. IsAvailable describes the current proven host state.

Does registration contact the network?

No. Registration and the supplied diagnostic probe perform no downloads, provider calls, subprocess execution, or remote inference.