winforms
- Repo stars 423
- Author repo dotnet-skills
- Domain
- Design
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @managedcode · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Windows
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Windows Forms
## Trigger On
- working on Windows Forms UI, event-driven workflows, or classic LOB applications
- migrating WinForms from .NET Framework to modern .NET
- cleaning up oversized form code or designer coupling
- implementing data binding, validation, or control customization
## Workflow
1. **Respect designer boundaries** — never edit `.Designer.cs` directly; changes are lost on regeneration.
2. **Separate business logic from forms** — use MVP (Model-View-Presenter) pattern. Forms orchestrate UI; presenters contain logic; services handle data access.
```csharp
// View interface — forms implement this
public interface ICustomerView
{
string CustomerName { get; set; }
event EventHandler SaveRequested;
void ShowError(string message);
}
// Presenter — testable without UI
public class CustomerPresenter
{
private readonly ICustomerView _view;
private readonly ICustomerService _service;
public CustomerPresenter(ICustomerView view, ICustomerService service)
{
_view = view;
_service = service;
_view.SaveRequested += async (s, e) =>
{
try { await _service.SaveAsync(_view.CustomerName); }
catch (Exception ex) { _view.ShowError(ex.Message); }
};
}
}
```
3. **Use DI from Program.cs** (.NET 6+):
```csharp
var services = new ServiceCollection();
services.AddSingleton<ICustomerService, CustomerService>();
services.AddTransient<MainForm>();
using var sp = services.BuildServiceProvider();
Application.Run(sp.GetRequiredService<MainForm>());
```
4. **Use data binding** via `BindingSource` and `INotifyPropertyChanged` instead of manual control population. See [references/patterns.md](references/patterns.md) for complete binding patterns.
5. **Use async/await** for I/O operations — disable controls during loading, use `Progress<T>` for progress reporting. Never block the UI thread.
6. **Validate with `ErrorProvider`** and the `Validating` event. Call `ValidateChildren()` before save operations.
7. **Modernize incrementally** — prefer better structure over big-bang rewrites. Use .NET 8+ features (button commands, stock icons) when available.
```mermaid
flowchart LR
A["Form event"] --> B["Presenter handles logic"]
B --> C["Service layer / data access"]
C --> D["Update view via interface"]
D --> E["Validate and display results"]
```
## Key Decisions
| Decision | Guidance |
|----------|----------|
| MVP vs MVVM | Prefer MVP for WinForms — simpler with event-driven model |
| BindingSource vs manual | Always prefer BindingSource for list/detail binding |
| Sync vs async I/O | Always async — use `async void` only for event handlers |
| Custom controls | Extract reusable `UserControl` when form grows beyond ~300 lines |
| .NET Framework → .NET | Use the official migration guide; validate designer compatibility first |
## Deliver
- less brittle form code with clear UI/logic separation
- MVP pattern with testable presenters
- pragmatic modernization guidance for WinForms-heavy apps
- data binding and validation patterns that reduce manual wiring
## Validate
- designer files stay stable and are not hand-edited
- forms are not acting as the application service layer
- async operations do not block the UI thread
- validation is implemented consistently with ErrorProvider
- Windows-only runtime behavior is tested on target
## References
- [references/patterns.md](references/patterns.md) - WinForms architectural patterns (MVP, MVVM, Passive View), data binding, validation, form communication, threading, DI setup, and .NET 8+ features
- [references/migration.md](references/migration.md) - step-by-step migration from .NET Framework to modern .NET, common issues, deployment options, and gradual migration strategies
Sections and files
Listed in source order.
sections -> Trigger On → Workflow → Key Decisions → Deliver → Validate → References
terms -> Respect designer boundaries · Separate business logic from forms · Use DI from Program.cs · Use data binding · Use async/await · Validate with ErrorProvider · Modernize incrementally
files/cmd -> .Designer.cs · BindingSource · INotifyPropertyChanged · Progress<T> · ErrorProvider · Validating · ValidateChildren() · async void
body sha256 -> 5346fe3182cf
Trigger On
working on Windows Forms UI, event-driven workflows, or classic LOB applications migrating WinForms from .NET Framework to modern .NET cleaning up oversized form code or designer coupling implementing data binding, validation, or control customization
Workflow
Respect designer boundaries — never edit
.Designer.csdirectly; changes are lost on regeneration. Separate business logic from forms — use MVP (Model-View-Presenter) pattern. Forms orchestrate UI; presenters contain logic; services handle data access. Use DI from Program.cs (.NET 6+): Use data binding viaBindingSourceandINotifyPropertyChangedinstead of manual control population. See references/patterns.md for complete binding patterns.Key Decisions
Decision · Guidance MVP vs MVVM · Prefer MVP for WinForms — simpler with event-driven model BindingSource vs manual · Always prefer BindingSource for list/detail binding Sync vs async I/O · Always async — use
async voidonly for event handlers Custom controls · Extract reusableUserControlwhen form grows beyond ~300 linesDeliver
less brittle form code with clear UI/logic separation MVP pattern with testable presenters pragmatic modernization guidance for WinForms-heavy apps data binding and validation patterns that reduce manual wiring
Validate
designer files stay stable and are not hand-edited forms are not acting as the application service layer async operations do not block the UI thread validation is implemented consistently with ErrorProvider Windows-only runtime behavior is tested on target