Comment by pjmlp

No they aren't placing all their chips on WinUI3, only those that never went through all reboots since Windows 8, believe that.

WPF got taken out of legacy mode at BUILD 2024, exactly because hardly anyone outside Redmond cares about WinUI 3.

Anyone that has been long enough around, has seen ASP.NET MVC 5, ASP.NET Core MVC (not compatible with MVC 5 predecessor), Razor Pages, Minimal APIs, Blazor,...

So it is a mess doing consulting and depending on what .NET version the customer team is allowed to use, and existing code, what gets to be used by that portfolio.

Minimal APIs have been designed to bring in Python and JavaScript developers into .NET, which many of us see as not working at all, while having created the need now everyone creates their own controllers infractruture, as means to tame having minimal APIs all over the place, there are even MVVM like frameworks now for that purpose.

Blazor is really only usable as path forward for those still stuck in WebForms, due to the similar approach to do Web UIs, and to .NET shops without frontend teams.

In the age of distributed computing with microservices and frontend teams, it is a hard sell to make them adopt Blazor and learn C#, instead of React, Angular, Vue.

At least they have adopted TypeScript, the next language that Anders Hejlsberg decided to focus on.

Aspire is something that has been pivoted, now they try to sell it as Microsoft's Pulumi, but everyone has to write the orchestration code in C#, thus only relevant to .NET shops.

Maddy Montaquila has said in a few .NET podcast interviews that they are trying to use Aspire as means to sell .NET to UNIX shops, given the low adoption numbers outside the traditional Microsoft shops, even after almost a decade being open source.