[Documentation] Update ONNX Runtime Documentation to Position WinML as Preferred Windows Path and DirectML in Sustained Engineering (#25901)
This PR addresses issue #25899 by updating the ONNX Runtime
documentation to clearly reflect that WinML is the preferred and
future-safe execution path for Windows developers, with DirectML now in
sustained engineering rather than deprecated.
## Changes Made
### DirectML Execution Provider Page
- Updated messaging to use "sustained engineering" terminology,
clarifying that DirectML continues to be supported but new feature
development has moved to WinML
- Maintained clear migration guidance directing users to WinML with
links to installation instructions
- Preserved existing technical documentation for users who still need
DirectML information
### Windows Getting Started Page
- Updated the introduction to explicitly state "WinML is the recommended
Windows development path for ONNX Runtime"
- Enhanced developer guidance explaining WinML's key benefits:
- Uses the same ONNX Runtime APIs developers are familiar with
- WinML automatically selects the best execution provider based on
customer's hardware, with override mechanisms for manual fine-grained
control
- Simplified deployment by deploying all needed dependencies for AI
inference on the client
- Added comprehensive Windows version support clarification:
- Windows 10 (1809+) & Windows 11 (before 24H2): ONNX Runtime works but
requires manual execution provider management
- Windows 11 (24H2+): WinML provides additional automation for execution
provider selection and hardware optimization
- Corrected namespace reference to
Microsoft.Windows.AI.MachineLearning.dll
### Install Page
- Updated installation instructions to consistently use sustained
engineering terminology for DirectML
- Enhanced WinML visibility by maintaining "recommended for Windows"
designation
- Updated both inline installation sections and comprehensive install
table with consistent messaging
- Added guidance note to Python DirectML section directing new projects
to consider WinML
## Impact
These changes provide clearer, more accurate guidance for Windows
developers on the preferred ONNX Runtime deployment path while
maintaining backward compatibility documentation. The updates help
developers understand:
- DirectML's current sustained engineering status (supported but
innovation moved to WinML)
- WinML's relationship to ONNX Runtime with clear version requirements
and capabilities
- The benefits of using WinML over DirectML, including automatic
hardware optimization with manual override options
- Precise Windows version support breakdown for different deployment
scenarios
- Where to find additional resources and migration paths
The documentation changes preserve all existing content while providing
the necessary updated guidance based on Microsoft's current Windows AI
strategy.
Fixes #25899
<!-- START COPILOT CODING AGENT SUFFIX -->
<!-- START COPILOT CODING AGENT TIPS -->
---
✨ Let Copilot coding agent [set things up for
you](https://github.com/microsoft/onnxruntime/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot)
— coding agent works faster and does higher quality work when set up for
your repo.
---------
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: MaanavD <24942306+MaanavD@users.noreply.github.com>