WPF Service Generator

WPF Service Generator

If $0 is empty, use the AskUserQuestion tool to ask: "Enter the Service name (e.g., DataExport, FileManager)". Do NOT proceed until a valid name is provided. Use the response as the ServiceName for all subsequent steps.

Generate a $0Service with interface + implementation class + DI registration. Automatically places files in the correct project based on solution structure. If --no-interface is appended, skip interface generation.

• Replace {Namespace} with the project's root namespace detected from csproj or existing code.

Usage

# Interface + Implementation + DI registration
/wpf-dev-pack:make-wpf-service DataExport

# Implementation only (no interface) — for simple services
/wpf-dev-pack:make-wpf-service FileManager --no-interface

---

Execution Procedure

Step 1: Parse $0

• $0 is the service name (without Service suffix — auto-appended)
  • e.g., DataExport → IDataExportService.cs + DataExportService.cs
• --no-interface flag: Skip interface generation (class-only)

Step 2: Locate Target Projects

Search for solution file and identify projects by naming convention:

Project Suffix	Purpose	Files Placed
.Abstractions	Interfaces	I$0Service.cs
.Core	Business logic	$0Service.cs (UI-independent)
.WpfServices	WPF-dependent services	$0Service.cs (if needs WPF types)
.WpfApp	Application	DI registration in App.xaml.cs

Fallback rules:

• No .Abstractions project → place interface in Services/ folder of main project
• No .Core or .WpfServices → place implementation in Services/ folder of main project
• Single project solution → all files in Services/ folder

Step 3: Generate Interface (unless --no-interface)

Create I$0Service.cs:

namespace {Namespace}.Services;

public interface I$0Service
{
    // TODO: Define service contract
    // TODO: 서비스 계약 정의
}

Step 4: Generate Implementation

Create $0Service.cs:

namespace {Namespace}.Services;

public sealed class $0Service : I$0Service
{
    // TODO: Implement service
    // TODO: 서비스 구현
}

If --no-interface:

namespace {Namespace}.Services;

public sealed class $0Service
{
    // TODO: Implement service
    // TODO: 서비스 구현
}

Step 5: Register in DI Container

CommunityToolkit.Mvvm (GenericHost)

Locate App.xaml.cs and add in ConfigureServices:

// With interface
services.AddSingleton<I$0Service, $0Service>();

// Without interface (--no-interface)
services.AddSingleton<$0Service>();

Prism 9

Locate App.xaml.cs and add in RegisterTypes:

// With interface
containerRegistry.RegisterSingleton<I$0Service, $0Service>();

// Without interface (--no-interface)
containerRegistry.RegisterSingleton<$0Service>();

Step 6: Report Results

Output list of generated/modified files and next steps guidance.

---

Generated File Structure

With Interface (default)

{AbstractionsProject}/
└── Services/
    └── I$0Service.cs

{CoreProject}/
└── Services/
    └── $0Service.cs

{WpfAppProject}/
└── App.xaml.cs              (DI registration added)

Without Interface (--no-interface)

{CoreProject}/
└── Services/
    └── $0Service.cs

{WpfAppProject}/
└── App.xaml.cs              (DI registration added)

---

Error Handling

• Missing service name → output usage instructions
• No WPF project found → suggest /wpf-dev-pack:make-wpf-project first
• Duplicate service → warn and abort
• Multiple candidate projects → ask user which to use