wpf-devexpress-loading-indicators

Implement splash screens and loading indicators in WPF apps using DevExpress controls.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/AleksaRistic216/dotnet-playground --skill wpf-devexpress-loading-indicators-aleksaristic216
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wpf-devexpress-loading-indicators
Source: https://github.com/AleksaRistic216/dotnet-playground/tree/main/.github/skills/wpf/wpf-devexpress-loading-indicators
Command: npx skills add https://github.com/AleksaRistic216/dotnet-playground --skill wpf-devexpress-loading-indicators-aleksaristic216

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires DevExpress.Wpf.Core, DevExpress.Wpf.ThemesLW, and includes references (resource) components.

What problem does it solve? Choosing and wiring the right loading indicator in a WPF application is error-prone: some indicators freeze when the main UI thread blocks, others lock the wrong part of the window, and the legacy DXSplashScreen API is deprecated. This Skill guides correct selection and implementation of the three DevExpress WPF loading indicators. ## Core Features & Use Cases - SplashScreenManager: Show a startup or long-operation splash screen that runs on a separate UI thread, with themed, Fluent, or wait-indicator styles and runtime progress updates via DXSplashScreenViewModel. - LoadingDecorator: Wrap any slow-loading region (grid, chart, panel) so an indicator appears while content loads, with OwnerLock modes controlling what input is blocked. - WaitIndicator: Toggle a simple inline busy indicator with bindable DeferedVisibility for quick async operations. - Use Case: A developer needs a startup splash that keeps animating while the app loads 10 million rows on the main thread; the Skill directs them to SplashScreenManager.CreateThemed(...).ShowOnStartup() with the theme applied first. ## Quick Start Ask the AI to add a themed startup splash screen to your WPF app using DevExpress SplashScreenManager with ShowOnStartup.

Frequently Asked Questions about wpf-devexpress-loading-indicators

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I show a splash screen at WPF app startup with DevExpress?

Call SplashScreenManager.CreateThemed(new DXSplashScreenViewModel {...}).ShowOnStartup() in the App constructor. Set ApplicationThemeHelper.ApplicationThemeName first so the splash picks up theme colors, and it auto-closes when the main window loads.

SplashScreenManager vs LoadingDecorator vs WaitIndicator in WPF?

SplashScreenManager runs on a separate UI thread for startup and blocking operations. LoadingDecorator wraps a slow-loading region with configurable OwnerLock input blocking. WaitIndicator is a simple inline spinner toggled via DeferedVisibility on the main thread.

Why does my WPF loading indicator freeze during long operations?

LoadingDecorator and WaitIndicator run on the main UI thread, so they freeze when it blocks. Use SplashScreenManager, which runs on a separate UI thread and keeps animating, or refactor the work to async.

Does DevExpress WPF loading indicator support .NET 8?

Yes, all three indicators support .NET 6/7/8+ targeting Windows (net8.0-windows) and .NET Framework 4.6.2+. Install the DevExpress.Wpf.Core NuGet package; a valid DevExpress license is required.

How do I migrate from DXSplashScreen to SplashScreenManager?

Replace DXSplashScreen.Show<T>() with SplashScreenManager.CreateThemed(...).ShowOnStartup() or .Show(), and DXSplashScreen.Close() with the instance Close() or static CloseAll(). Both run on a separate UI thread, so migration is mostly an API rename.

Why is 'Application' an ambiguous reference in App.xaml.cs?

DevExpress.Wpf.Core transitively references System.Windows.Forms, and ImplicitUsings on .NET 6+ makes Application ambiguous. Qualify it as System.Windows.Application in App.xaml.cs to resolve the CS0104 error.