Showing category results for WinForms

Feb 24, 2026
Post comments count6
Post likes count8

The Dongle Died at Midnight – WinForms Agent Saved my German Mom’s Business Trip

Klaus Loeffelmann
Klaus Loeffelmann

Vibe Coding. IntelliSense on Steroids. Intention-Based Development. Call it what makes you happy - it's "just" the next evolutionary step in software development for me. Which let me build my stranded 82-year-old retirement-resistant mom an ersatz time-study app when her dongle died at midnight.

.NETAIWinForms
Nov 11, 2025
Post comments count15
Post likes count50

Announcing .NET 10

.NET Team
.NET Team

Announcing the release of .NET 10, the most productive, modern, secure, intelligent, and performant release of .NET yet. With updates across ASP.NET Core, C# 14, .NET MAUI, Aspire, and so much more.

.NETASP.NET CoreC#
Jan 21, 2025
Post comments count2
Post likes count3

WinForms: Analyze This (Me in Visual Basic)

Klaus Loeffelmann
Klaus Loeffelmann

Your WinForms code might have issues—maybe an Async call picked the wrong overload, or it’s leaking data into resource files. Time to call in a code-shrink! So, WinForms, Analyze This!

.NETWinForms
Dec 10, 2024
Post comments count8
Post likes count11

Invoking Async Power: What Awaits WinForms in .NET 9

Klaus Loeffelmann
Klaus Loeffelmann

With .NET 9, we’re bringing a suite of new async APIs to WinForms, aimed at making UI updates, dialog interactions, and control management more efficient.

.NETWinForms
Nov 12, 2024
Post comments count30
Post likes count44

Announcing .NET 9

.NET Team
.NET Team

Announcing the release of .NET 9, the most productive, modern, secure, intelligent, and performant release of .NET yet. With updates across ASP.NET Core, C#, .NET MAUI, .NET Aspire, and so much more.

.NETASP.NET CoreC#
Feb 22, 2024
Post comments count29
Post likes count12

WinForms in a 64-Bit world – our strategy going forward

Klaus Loeffelmann
Klaus Loeffelmann

32-bit components can impose challenges for WinForms developers in a 64-bit Visual Studio environment, but there are options to solve this. Component modernization, migrating to .NET 6+ and a new option to use the out-of-process Designer for Framework are the key to a feasible way forward!

.NET.NET FrameworkWinForms