AIRoutine.CodeStyle.Analyzers 1.5.1

AIRoutine.CodeStyle.Analyzers

Roslyn-based C# code analyzers for strict code style enforcement with IDE integration.

Rules

ACS0001: No Hardcoded Strings

Detects hardcoded strings in files matching these patterns:

• *ViewModel.cs
• *Service.cs
• *Handler.cs

Allowed Exceptions

Example

// Bad - ACS0001
public class UserViewModel
{
    public string Title => "Welcome";  // Error
}

// Good
public class UserViewModel
{
    private const string DefaultTitle = "Welcome";  // OK
    public string Title => _localizer["WelcomeTitle"];  // OK
}

ACS0002: No Static Calls

Enforces dependency injection by forbidding static method calls on non-framework types.

Allowed

• System.* namespace (Console, Math, Path, etc.)
• Microsoft.* namespace
• Windows.* namespace
• Testing frameworks (Xunit, NUnit, Moq, etc.)
• Extension methods
• Enum values
• Calls to same type (factory methods)

Example

// Bad - ACS0002
public class OrderService
{
    public string Process() => MyHelper.Calculate();  // Error
}

// Good
public class OrderService
{
    private readonly IHelper _helper;
    public OrderService(IHelper helper) => _helper = helper;
    public string Process() => _helper.Calculate();  // OK (DI)
    public string GetPath() => Path.Combine("a", "b");  // OK (System)
}

ACS0003: No Hardcoded Colors

Detects hardcoded colors in C# code. Colors should be defined in ResourceDictionary.

Detected Patterns

• Colors.Red, Colors.Blue, etc.
• Color.FromArgb(...), Color.FromRgb(...)
• new SolidColorBrush(Colors.*)
• Color.Parse("#FFFFFF")
• ColorHelper.FromArgb(...)

Example

// Bad - ACS0003
public Color GetColor() => Colors.Red;  // Error
public Color Custom() => Color.FromArgb(255, 100, 150, 200);  // Error

// Good
public Color GetColor() => (Color)Application.Current.Resources["PrimaryColor"];

ACS0012: No ICommand Properties

Forbids direct ICommand property declarations in ViewModel/Model classes. Commands must be defined using the [UnoCommand] attribute on methods instead.

Detected Patterns

• public ICommand MyCommand { get; }
• public IRelayCommand Command { get; }
• public AsyncRelayCommand SaveCommand { get; }
• Any property implementing System.Windows.Input.ICommand

Applies To

Classes ending with:

• *ViewModel (MVVM pattern)
• *Model (MVUX pattern)

Example

// Bad - ACS0012
public class MainViewModel
{
    public ICommand SaveCommand { get; }  // Error
}

// Good
public class MainViewModel
{
    [UnoCommand]
    public void Save() { }  // OK - generates command automatically
}

ACS0013: No Forbidden Command Attributes

Forbids command attributes from other frameworks. Only [UnoCommand] is allowed.

Forbidden Attributes

• [RelayCommand] (CommunityToolkit.Mvvm)
• [AsyncRelayCommand] (CommunityToolkit.Mvvm)
• [Command] (various frameworks)
• [AsyncCommand]
• [DelegateCommand] (Prism)
• [ReactiveCommand] (ReactiveUI)

Example

// Bad - ACS0013
public class MainViewModel
{
    [RelayCommand]  // Error - use [UnoCommand] instead
    public void Save() { }
}

// Good
public class MainViewModel
{
    [UnoCommand]  // OK
    public void Save() { }
}

ACS0014: No Inline Visual Properties in C# Markup

Forbids setting visual properties inline in C# Markup. These should come from Style instead.

Forbidden Methods

• Spacing: .Padding(), .Margin()
• Colors: .Background(), .Foreground(), .BorderBrush(), .Fill(), .Stroke()
• Typography: .FontSize(), .FontWeight(), .FontFamily()
• Sizing: .CornerRadius(), .BorderThickness()

Example

// Bad - ACS0014
new Grid()
    .Padding(16)                                    // Error - use Style
    .Background(x => x.StaticResource("MyBrush"))   // Error - use Style

// Good - visual properties come from Style
new Grid()
    .Style(x => x.StaticResource("MyGridStyle"))    // Style defines Padding, Background, etc.

ACS0017: StaticResource Must Use Constants

Forbids hardcoded strings in .StaticResource() and .ThemeResource() calls. Resource keys must be constants from a *.Core.Styles project.

Allowed Constant Sources

Classes/namespaces containing: Styles, StyleKeys, ResourceKeys, ThemeKeys, BrushKeys, ColorKeys

Example

// Bad - ACS0017
.Style(x => x.StaticResource("BodyTextBlockStyle"))     // Error - hardcoded string
.Background(x => x.StaticResource("SurfaceBrush"))      // Error - hardcoded string

// Good - constants from Core.Styles project
.Style(x => x.StaticResource(StyleKeys.BodyTextBlock))  // OK
.Background(x => x.StaticResource(BrushKeys.Surface))   // OK

Required Project Structure

MyApp.Core.Styles/
├── StyleKeys.cs      // public const string BodyTextBlock = "BodyTextBlockStyle";
├── BrushKeys.cs      // public const string Surface = "SurfaceBrush";
└── ColorKeys.cs      // public const string Primary = "PrimaryColor";

ACS0015: C# Markup Style Required

Ensures UI controls in C# Markup have explicit Style assignments for consistent theming.

Applies To

Common UI controls: Button, TextBlock, TextBox, ListView, ComboBox, Border, etc.

Example

// Bad - ACS0015
new TextBlock()
    .Text("Hello");  // Error - missing Style

// Good
new TextBlock()
    .Style(x => x.StaticResource("BodyTextBlockStyle"))
    .Text("Hello");

ACS0016: C# Markup AutomationId Format

Validates that AutomationId values follow a consistent naming pattern for test automation.

Required Pattern

PageName.ControlType.Purpose or PageName.Purpose

Examples: LoginPage.Button.Submit, SettingsPage.Username, MainPage.Root

Example

// Bad - ACS0016
.AutomationProperties(ap => ap.AutomationId("submit"))  // Error
.AutomationProperties(ap => ap.AutomationId("btn_submit"))  // Error

// Good
.AutomationProperties(ap => ap.AutomationId("LoginPage.Button.Submit"))  // OK
.AutomationProperties(ap => ap.AutomationId("FooterPage.Root"))  // OK

Installation

<PackageReference Include="AIRoutine.CodeStyle.Analyzers" Version="1.1.0" PrivateAssets="all" />

IDE Integration

These analyzers provide real-time feedback in Visual Studio, VS Code, and Rider:

• Squiggly underlines for violations
• Error messages in Error List / Problems panel
• Build failures for violations (Severity: Error)

Code Fixes

All rules include automatic code fixes accessible via the light bulb menu (Ctrl+.):