make-wpf-service

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 (keep the interface visible to both the implementation and the app):

• No .Abstractions project → place the interface in .Core (beside the implementation). Do NOT put it in the WPF app project: .Core cannot reference the app, so an interface placed there is unreachable from the implementation in .Core.
• No .Core or .WpfServices (no separate logic project) → place both interface and implementation in the app's Services/ folder.
• Single project solution → both files in Services/ folder.