원클릭으로 Manus에서 모든 스킬 실행

designing-avalonia-customcontrol-architecture

스타36

포크5

업데이트2026년 1월 19일 03:30

Defines the basic solution structure for AvaloniaUI Desktop Applications using CustomControl. Use when creating new AvaloniaUI projects or designing stand-alone control styles with ControlTheme.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

christian289

christian289/dotnet-with-claudecode

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

6.5 Writing AXAML Code

When generating AXAML code, use CustomControl with ControlTheme for Stand-Alone Control Style
Purpose: Theme separation and minimizing style dependencies

6.5.1 AvaloniaUI Custom Control Library Project Structure

Recommended Project Structure:

YourAvaloniaSolution
├── YourCustomControlProject1/
│    ├── Properties/
│    │   ├── AssemblyInfo.cs            ← AssemblyInfo.cs definition
│    ├── Themes/
│    │   ├── Generic.axaml            ← ControlTheme definition
│    │   ├── CustomButton1.axaml       ← Individual control theme
│    │   └── CustomTextBox1.axaml      ← Individual control theme
│    ├── CustomButton1.cs
│    └── CustomTextBox1.cs
└── YourCustomControlProject2/
    ├── Properties/
    │   ├── AssemblyInfo.cs            ← AssemblyInfo.cs definition
    ├── Themes/
    │   ├── Generic.axaml            ← ControlTheme definition
    │   ├── CustomButton2.axaml       ← Individual control theme
    │   └── CustomTextBox2.axaml      ← Individual control theme
    ├── CustomButton2.cs
    └── CustomTextBox2.cs

6.6 ⚠️ Distinguishing ResourceInclude vs MergeResourceInclude

ResourceInclude: Used in regular ResourceDictionary files (Generic.axaml, Styles, etc.)
MergeResourceInclude: Used only in Application.Resources (App.axaml)

Advantages:

Complete separation of theme and logic based on ControlTheme
Flexible style variations through CSS Classes
State management via Pseudo Classes (:pointerover, :pressed, etc.)
Theme modularization through ResourceInclude
Work can be split by file for team collaboration

6.5.2 Key Differences Between WPF and AvaloniaUI

Item	WPF	AvaloniaUI
File Extension	.xaml	.axaml
Style Definition	Style + ControlTemplate	ControlTheme
State Management	Trigger, DataTrigger	Pseudo Classes, Style Selector
CSS Support	❌	✅ (Classes attribute)
Resource Merging	MergedDictionaries + ResourceDictionary	MergedDictionaries + ResourceInclude
Dependency Props	DependencyProperty	StyledProperty, DirectProperty

이 저장소의 다른 Skills

같은 저장소

wpf-rule-converter-patterns

christian289/dotnet-with-claudecode

WPF IValueConverter rules: MarkupExtension singleton, pure functions, null/UnsetValue handling, TemplateBinding.

2026-06-2436

wpf-rule-freezable-performance

christian289/dotnet-with-claudecode

WPF Freezable performance rules: Freeze() all Brush/Pen/Geometry; create-and-freeze in constructor, reuse in OnRender.

2026-06-2436

wpf-rule-mvvm-constraints

christian289/dotnet-with-claudecode

WPF MVVM layer-separation rules: no System.Windows in ViewModels, BCL-only types, CommunityToolkit.Mvvm base classes. Preloaded into MVVM-related wpf-dev-pack agents.

2026-06-2436

wpf-rule-prohibitions

christian289/dotnet-with-claudecode

Banned wpf-dev-pack patterns (P-001..P-004): ViewModelLocator, code-behind DataContext, Stateless ViewModel, mixing composition paths.

2026-06-2436

wpf-rule-rendering-antipatterns

christian289/dotnet-with-claudecode

WPF rendering anti-patterns: no InvalidateVisual in loops, no resource allocation in OnRender.

2026-06-2436

wpf-rule-resourcedictionary-patterns

christian289/dotnet-with-claudecode

WPF ResourceDictionary rules: Generic.xaml as MergedDictionaries hub only, per-control style files, resource order.

2026-06-2436

name	designing-avalonia-customcontrol-architecture
description	Defines the basic solution structure for AvaloniaUI Desktop Applications using CustomControl. Use when creating new AvaloniaUI projects or designing stand-alone control styles with ControlTheme.

6.5 Writing AXAML Code

When generating AXAML code, use CustomControl with ControlTheme for Stand-Alone Control Style
Purpose: Theme separation and minimizing style dependencies

6.5.1 AvaloniaUI Custom Control Library Project Structure

Recommended Project Structure:

YourAvaloniaSolution
├── YourCustomControlProject1/
│    ├── Properties/
│    │   ├── AssemblyInfo.cs            ← AssemblyInfo.cs definition
│    ├── Themes/
│    │   ├── Generic.axaml            ← ControlTheme definition
│    │   ├── CustomButton1.axaml       ← Individual control theme
│    │   └── CustomTextBox1.axaml      ← Individual control theme
│    ├── CustomButton1.cs
│    └── CustomTextBox1.cs
└── YourCustomControlProject2/
    ├── Properties/
    │   ├── AssemblyInfo.cs            ← AssemblyInfo.cs definition
    ├── Themes/
    │   ├── Generic.axaml            ← ControlTheme definition
    │   ├── CustomButton2.axaml       ← Individual control theme
    │   └── CustomTextBox2.axaml      ← Individual control theme
    ├── CustomButton2.cs
    └── CustomTextBox2.cs

6.6 ⚠️ Distinguishing ResourceInclude vs MergeResourceInclude

ResourceInclude: Used in regular ResourceDictionary files (Generic.axaml, Styles, etc.)
MergeResourceInclude: Used only in Application.Resources (App.axaml)

Advantages:

Complete separation of theme and logic based on ControlTheme
Flexible style variations through CSS Classes
State management via Pseudo Classes (:pointerover, :pressed, etc.)
Theme modularization through ResourceInclude
Work can be split by file for team collaboration

6.5.2 Key Differences Between WPF and AvaloniaUI

Item	WPF	AvaloniaUI
File Extension	.xaml	.axaml
Style Definition	Style + ControlTemplate	ControlTheme
State Management	Trigger, DataTrigger	Pseudo Classes, Style Selector
CSS Support	❌	✅ (Classes attribute)
Resource Merging	MergedDictionaries + ResourceDictionary	MergedDictionaries + ResourceInclude
Dependency Props	DependencyProperty	StyledProperty, DirectProperty