None of this is a part of .NET itself, rather a part of ecosystem of its libraries, like ASP.NET Core, EF Core, etc. Again: it is not a part of the language or

None of this is a part of .NET itself, rather a part of ecosystem of its libraries, like ASP.NET Core, EF Core, etc. Again: it is not a part of the language or runtime. If you do, however, have links to code changes that prove otherwise - please do post them. Meanwhile, COM interests only a limited part of community, and there also exists actively maintained https://github.com/microsoft/CsWin32 https://github.com/microsoft/CsWin32 A popular (if not the most, depending on location) choice to use EF Core with is PostgreSQL. Meanwhile, ASP.NET Core simply continues to evolve just like other libraries, whether they are a part of dotnet/* or not. GUI continues to get better with development of AvaloniaUI, Uno and MAUI. .NET as a whole is way bigger than some of it's "first-party" solutions that you don't even have to use, that have little impact on language, runtime and compiler themselves aside from "this is a good demonstration where we can improve the general case". There also exists Unity, many companies using completely non-standard stacks on top of the language, etc. But you deliberately choose to ignore this information for unknown reasons. It is genuinely bewildering to see this kind of flawed and strange impression of the ecosystem not rooted in reality. I suppose addressing this involves reading documentation and source material, which perhaps proves too challenging.