C# API reference
Browse the complete C# API reference for type declarations, constructors, properties, methods, events, and enums. Each type page includes the library's XML documentation and links to related types.
| Namespace | What to find there |
|---|---|
Fluence.Wpf | Theme and accent managers, theme watcher, enums, event arguments, typography helpers |
Fluence.Wpf.Controls | Windows, controls, attached-property helpers, and layout primitives |
Fluence.Wpf.Markup | ThemeResourceExtension, ThemeDictionary, and related dictionary types |
Fluence.Wpf.Automation | UI Automation peers for custom controls |
Common starting points
| Task | API | Usage guide |
|---|---|---|
| Create a window | FluenceWindow, TitleBar | Window and title bar |
| Construct a visual tree in code | Button, StackPanel | Create controls in C# |
| Set a theme | ApplicationThemeManager, SystemThemeWatcher | Theme and accent |
| Choose an accent | ApplicationAccentColorManager | Theme resources |
| Show a dialog | ContentDialog | Dialogs and feedback |
| Navigate between pages | NavigationView, TabView | Navigation and tabs |
For visual examples, use the control catalog. The gallery XAML and code-behind provide runnable examples.
Member scope
API pages document the members declared by each Fluence type. They also identify its base type: inherited WPF members such as Window.Show, Button.Click, and FrameworkElement.DataContext remain part of the control's API. Protected members are intended for derived controls.
For dependency properties, the CLR property is usually the value an application sets. The corresponding static ...Property field identifies that dependency property for binding, metadata, and dynamic resource references. Attached properties use their documented Get... and Set... methods.
Template and resource contracts
Default control templates live in Themes/Controls/ and are merged by Themes/Generic.xaml. A template's named parts and visual states are documented on its CLR type and in its template. Those implementation details can change when the control changes. The supported application-wide color, brush, typography, and metric keys are described in the theme resource reference.
The PowerShell command reference is separate from the CLR API. It is generated from the exported functions' comment-based help.