---
source_files:
  - Common/DTS.Common/obj/x86/Debug/BusyIndicatorManager/xBusyIndicator.g.i.cs
  - Common/DTS.Common/obj/x86/Debug/BusyIndicatorManager/xBusyIndicator.g.cs
generated_at: "2026-04-17T16:06:29.964296+00:00"
model: "zai-org/GLM-5-FP8"
schema_version: 1
sha256: "277de59d12cd489a"
---

# BusyIndicatorManager

### Purpose
This module contains auto-generated WPF code-behind for the `xBusyIndicator` control, which extends the Xceed Wpf Toolkit's `BusyIndicator`. It serves as the compiled representation of the XAML file `BusyIndicatorManager/xBusyIndicator.xaml`, enabling the WPF runtime to load and connect the XAML-defined UI elements. This is build infrastructure output, not hand-authored code.

### Public Interface
- **`xBusyIndicator`** (class) - Partial class extending `Xceed.Wpf.Toolkit.BusyIndicator` and implementing `System.Windows.Markup.IComponentConnector`.
  - `void InitializeComponent()` - Loads the XAML component from `/DTS.Common;component/busyindicatormanager/xbusyindicator.xaml`. Guards against multiple initialization via `_contentLoaded` flag.
  - `void IComponentConnector.Connect(int connectionId, object target)` - Explicit interface implementation for XAML element connection. Sets `_contentLoaded = true` but performs no other connection logic in this generated version.

### Invariants
- `_contentLoaded` field must remain `false` until `InitializeComponent()` is called.
- `InitializeComponent()` must be called before the control is displayed (standard WPF pattern).
- The XAML resource at the relative URI must exist in the assembly for `LoadComponent` to succeed.

### Dependencies
- **Depends on:** `Xceed.Wpf.Toolkit.BusyIndicator` (third-party control library), `System.Windows` (WPF framework), `System.Windows.Markup.IComponentConnector`.
- **Depended on by:** Cannot be determined from generated code alone; likely used by views requiring a busy/loading indicator overlay.

### Gotchas
- This is auto-generated code from `PresentationBuildTasks`. Manual edits will be overwritten on rebuild.
- The `Connect` method appears to have no named element connections (connectionId is unused), suggesting the XAML may have no named elements requiring code-behind access, or this is an intermediate build artifact.
- The `.g.cs` and `.g.i.cs` files are duplicate outputs (identical content) - this is normal for WPF build process but indicates intermediate build artifacts rather than final source.

---