https://thedotnetblog.com/tags/command-palette/Articles, tutorials and insights from the .NET community.Hugoen@thedotnetblog (The .NET Blog)@thedotnetblogMon, 15 Jun 2026 00:00:00 +0000https://thedotnetblog.com/news/emiliano-montesdeoca/powertoys-0100-dotnet-10-command-palette/Mon, 15 Jun 2026 00:00:00 +0000Emiliano Montesdeocahttps://thedotnetblog.com/news/emiliano-montesdeoca/powertoys-0100-dotnet-10-command-palette/PowerToys 0.100 is not a pure .NET story, but the .NET 10 upgrade, Command Palette improvements, and developer-focused workflow polish make it worth a closer look for Windows-based developers.<p>At first glance, <strong>PowerToys 0.100</strong> looks like one of those updates you skim, nod at, and move on.</p> <p>But I think there is a decent developer story hiding in here.</p> <p>No, this is not a framework release. And no, it is not directly about application code. But when a tool that many Windows developers keep open all day gets a <strong>.NET 10 upgrade</strong>, a stronger <strong>Command Palette</strong>, and better extension and workflow ergonomics, I think it earns at least a second look.</p> <h2 id="the-net-10-move-is-the-quiet-signal">The .NET 10 move is the quiet signal</h2> <p>One of the more interesting notes in the release is that PowerToys has now moved to <strong>.NET 10</strong>.</p> <p>That matters less because users will feel the runtime name directly, and more because it reflects platform confidence and ongoing modernization in one of Microsoft’s most visible Windows utility suites.</p> <p>I always pay attention when real tools adopt the newer runtime early. It tells you something about ecosystem readiness, performance confidence, and where internal engineering energy is going.</p> <h2 id="command-palette-keeps-becoming-more-relevant">Command Palette keeps becoming more relevant</h2> <p>The bigger user-facing story is probably the new <strong>Extension Gallery</strong> and improved Dock support in Command Palette.</p> <p>This is interesting because it keeps pushing PowerToys toward something more than a collection of utilities. It is becoming more like a customizable productivity surface.</p> <p>For developers, that matters when you start thinking in terms of:</p> <ul> <li>quick actions</li> <li>custom launch points</li> <li>multi-monitor workflows</li> <li>extension-driven tasks</li> </ul> <p>This is not the same thing as the AI-heavy command experiences we are seeing elsewhere, but it sits in a nearby space: tools that reduce friction between intent and action.</p> <h2 id="why-i-think-this-still-fits-the-blog">Why I think this still fits the blog</h2> <p>The reason I would keep an eye on releases like this is simple: good development experience is not only about the compiler or the IDE.</p> <p>It is also about the utilities around your day-to-day environment.</p> <p>When those tools improve:</p> <ul> <li>your context switching drops</li> <li>your workstation setup gets smoother</li> <li>your repeat actions get faster</li> <li>your customization options grow</li> </ul> <p>That may not sound dramatic, but it adds up over time.</p> <h2 id="my-take">My take</h2> <p>PowerToys 0.100 is not a must-cover release for every .NET developer.</p> <p>But if you work on Windows all day, use Command Palette heavily, or just like keeping an eye on where Microsoft’s desktop developer utilities are heading, there is enough here to care about.</p> <p>The .NET 10 upgrade alone makes it more than a casual mention.</p> <p>Original post: <a href="https://devblogs.microsoft.com/commandline/powertoys-0-100-is-here-new-shortcut-guide-command-palette-improvements-and-much-more/">PowerToys 0.100 is here: new Shortcut Guide, Command Palette improvements and much more!</a></p>