What problem does it solve?
Integrating the VisioForge Media Player SDK .NET into a WinUI 3 app is error-prone, especially around VideoView wiring, NuGet/redist setup, licensing, and common deployment failures like missing native DLLs or unsupported formats.
Core Features & Use Cases
- WinUI 3 VideoView integration: Host the SDK video output using
VisioForge.Core.UI.WinUI.VideoView over a Win2D CanvasControl, with the correct WinUI hosting pattern.
- File and stream playback: Play local files and network streams (HTTP/HTTPS/RTSP/UDP/file-based MMS) with transport controls (play/pause/resume/stop) and async operations.
- Format coverage and reliability: Use
MediaPlayerSourceMode.LAV with pinned NuGets and redist packages to reduce “filter not registered” and “codec not found” issues, plus guidance on what to do when a protocol like HLS/DASH isn’t supported.
- Production deployment and licensing: Register licenses via
SetLicenseCertificateAsync(byte[]), and avoid MSIX packaging pitfalls that can drop required native DLLs.
Quick Start
Configure a WinUI 3 desktop app to use the pinned NuGet packages for VisioForge.DotNet.MediaPlayer plus the WinUI VideoView host and redist packages, then construct VideoView(canvasControl) and MediaPlayerCore with Source_Mode = MediaPlayerSourceMode.LAV, add your stream or file to the playlist, and call PlayAsync().