Learn about what's new in Windows Forms for .NET 9. New versions of Windows Forms are released yearly with .NET.

.NET 11 is here with C# 15, faster developer tools, runtime and library improvements, and new capabilities for web, mobile, desktop, and AI apps.

Convert worksheet content into web pages so users can share spreadsheet data with recipients who only need a browser.

Join us for .NET Conf 2026, a free, virtual developer event co-organized by the .NET community and Microsoft. Learn about the latest in .NET, C#, and Visual Studio from experts and community leaders.

Repo: fra00/a-isl-agents. I got tired of two extremes: **one-shot prompts** that disappear into the chat, and **hand-written specs** nobody maintains. **A-ISL** is an experiment in the middle: you describe the product in natural language; a coding agent writes a **reviewable Spec** in classic ISL (`.isl.md`); you accept it; then you **explicitly** ask another skill to **compile** that Spec into `bin-\<stack>/` (React, Blazor, WinForms, C# library, …). ### The agentic part (easy to miss) You do **not** hand-author ISL or the app. 1. Skill **`a-isl-spec-author`** → agent writes `*.isl.md` only 2. You review (product sense first — you don’t need to know the grammar) 3. Skill **`a-isl-compile`** → agent regenerates `bin-<stack>/` via a small runtime (builder → queue → packet → lock) Spec never auto-chains into `bin/`. That’s the whole point: **human gate** , not autopilot. Same Spec can compile to more than one stack without rewriting intent — see the sheet demo (React / Blazor / WinForms). ### Who decides what A-ISL does **not** invent the product. You decide behavior and accept the Spec. Wrong Spec that compiles is still “faithful.” That boundary is intentional. ### What we measured Internal bench (`tariffe-v2`, closed Domain/Logic rules, N=5): Campaign | Stack | First full-pass | Final ---|---|---|--- A-ISL | react-js | 5/5 | 5/5 Single prompt | react-js | 5/5 | 5/5 A-ISL | csharp | 5/5 | 5/5 Prompt (open DTO style) | csharp | **1/5** | 5/5 Prompt + same “prefer records” rule | csharp | **5/5** | 5/5 **Regression check, not a leaderboard.** On a small closed-rules task, Spec → Compile matches a single prompt (5/5 vs 5/5 on JS). On C#, a prompt that left DTO style open dropped to 1/5 on first pass; adding the same “prefer records” rule closed the gap. The expected payoff is on **large or multi-module projects** and on **change-via-Spec**. This bench does not demonstrate that; it only supports non-regression on a small closed oracle. Full honesty: evaluation.md. ### Hosts Runtime is agent-agnostic. Skills ship for Cursor, Claude Code, and GitHub Copilot (same text, synced). Day-to-day use and the bench were on **Cursor** ; other hosts are not separately tested yet. ### When it might pay off Modules, evolution via Spec, multi-stack. For a one-shot script, a normal prompt is enough — Spec→Compile costs more turns on purpose. ### Try it **Prerequisites:** Node.js 18+; for Blazor / WinForms sheet demos, a .NET SDK (WinForms needs Windows targeting). git clone https://github.com/fra00/a-isl-agents.git cd a-isl-agents && npm install && npm --prefix runtime/lint install # open in your agent → /a-isl-spec-author → review → /a-isl-compile Tutorial: docs/tutorial-first-project.md

My most popular app is a WinForms app called Windows Caffeinated and it does one small thing very well, keeps your display on. While that is nice, I frequently wish I could add some more. I believe…

sLocker UI kit for Flutter: the person's locker pickups and the locker map, on the sApp UI kit's scope, theme and strings. Changelog excerpt: ## SDK ### Customer side - **On sApp 0.2.5**: the customer packages and UI kits now build on sApp 0.2.5, so errors carry the response headers and the seconds to wait, and the native kits follow dark mode and the corner radius. ## UI kits ### Flutter, web, React, React Native, SwiftUI, Jetpack Compose, WPF and WinForms - **Locker map with pickup points**: the locker map can show the service provider's pickup point counters beside its smart lockers, read with the app key alone so nobody needs[...]