Weekly .NET Roundup: PowerShell 7.6 LTS and MAUI Map Clustering

by TechHub

This week's .NET updates landed where teams feel everyday friction: shells and editors that drive automation and debugging, and UI controls that need to stay responsive under real data. Building on last week's “apply updates” focus (.NET servicing guidance and the macOS VS Code debugger hotfix) plus “try new features” (.NET 11 Preview 2 wave), this week continues the same two-track story: a clearer production baseline for tooling and a Preview 2 feature that is easy to validate in apps.

PowerShell 7.6 LTS on .NET 10: production automation baseline, with shell and module refinements

PowerShell 7.6 is now GA as the next LTS release, built on .NET 10 (LTS), giving teams a stable target for production scripting and automation where predictable behavior matters. Like last week's servicing guidance (“keep runtime/tooling patched,” including the out-of-band .NET 10.0.5 VS Code macOS debugger fix), 7.6 provides a steadier baseline for build agents, automation runners, and operator scripts, especially for fleets standardizing on .NET 10 LTS. Alongside engine reliability and cross-platform consistency work, the release updates key in-box modules (PSReadLine, PSResourceGet, ThreadJob), so environments may see behavior changes simply by moving to 7.6 even if modules were not intentionally updated before. This mirrors last week's “hidden dependency” point: module and runtime layers are often where friction appears first, including on build agents and base images. Much of the polish is focused on interactive authoring and discoverability. Tab completion has many fixes and expansions (paths across providers, parameter value completions, more contexts where completion works, module completion by shortname), which reduces manual lookup and trial-and-error. Automation-visible updates include Get-Clipboard -Delimiter, Register-ArgumentCompleter -NativeFallback for native-command completion, Get-Command -ExcludeModule, New-Item treating -Target literally, and Start-Process -Wait improving polling efficiency to reduce overhead in scripts waiting on child processes. On platform conventions, 7.6 adds aliases PSForEach() and PSWhere() for intrinsic ForEach() and Where() methods and respects NO_COLOR for stderr output in the console host. API and compatibility updates include Unix SystemPolicy public APIs being visible but no-op for PowerShellStandard.Library, and certificate DNS name handling using X509SubjectAlternativeNameExtension.EnumerateDnsNames(). Several formerly optional or preview features are now treated as mainstream (PSFeedbackProvider, PSNativeWindowsTildeExpansion, PSRedirectToVariable, PSSubsystemPluginModel), which reduces “feature flag semantics” surprises in production. As with any LTS bump, there are breaking changes to validate: Join-Path changes -ChildPath to string[], WildcardPattern.Escape() now escapes lone backticks correctly (changing outputs for scripts relying on prior behavior), and the GetHelpCommand trace source name drops a trailing space (affecting trace-name matching). The post links install guidance and What's New docs and notes ongoing PowerShell 7.7 previews.

.NET MAUI 11 Preview 2: built-in map pin clustering for Android and iOS/Mac Catalyst

Following last week's .NET 11 Preview 2 rundown (including the MAUI Map control landing in Preview 2), this is one of the most visible additions in apps: .NET MAUI 11 Preview 2 adds built-in pin clustering in the Map control for Android and iOS/Mac Catalyst. With IsClusteringEnabled="True", overlapping pins collapse into cluster markers with a count when zoomed out, then expand as users zoom in, which improves usability and performance on crowded maps. The feature supports practical organization via ClusteringIdentifier strings per Pin: pins with the same identifier cluster together (for example, “coffee”), while different identifiers will not merge even if nearby (keeping “parks” separate). For interaction, Map exposes ClusterClicked; ClusterClickedEventArgs includes the cluster Pins, Location, and a Handled flag to suppress default zoom-to-cluster behavior (the sample shows listing pin labels via DisplayAlert). Under the hood, Android uses a custom grid-based algorithm recalculated on zoom changes and avoids external dependencies, while iOS/Mac Catalyst uses MapKit's native MKClusterAnnotation for platform-native behavior and animations. To try it you need .NET 11 Preview 2 and updated MAUI workloads; the post also calls out Visual Studio 2026 Insiders on Windows or VS Code with C# Dev Kit, continuing last week's “validate previews in real toolchains” guidance. Samples are updated (the maui-samples Maps demo adds a Clustering page) and Microsoft Learn docs are refreshed.

Other .NET News

Last week's .NET servicing roundup included the out-of-band macOS VS Code debugger fix, and this week's VS Code Insiders notes continue the “make the daily loop smoother” direction for cross-platform debugging and local workflows. VS Code Insiders kept refining cross-platform workflows that .NET teams tend to hit quickly. The integrated browser can now bypass certificate errors for localhost HTTPS with self-signed certs, which helps local secure-context loops (OAuth redirects, secure cookies, service workers) without switching browsers or reworking trust stores. Debug config sharing is cleaner with new launch.json top-level "windows", "linux", "osx" properties so repos can keep platform-specific entries in one file while hiding irrelevant configs on other OSes, reducing noise in the Run and Debug UI. There's also a WSL fix for “Reveal in File Explorer,” plus UX/accessibility improvements like better screen reader labels and image carousel zoom for inspecting assets.