3 ms·

What kind of decisions driven by Azure do you have in mind? What kind of impact does ASP.NET Core (or EF Core for that matter) have on CoreCLR and NativeAOT?

pjmlp 3y ago
The whole .NET 9 roadmap being driven by Aspire (works best on Azure) and Blazor. Stuff like minimal APIs driving C# features, e.g. lambda improvements required for replacing controllers with minimal APIs. There are hardly any desktop or COM improvements that are taken as seriously as the way the ASP.NET is. EF Core works best with Microsoft offerings, SQL Server, CosmoDB,.... The whole aspect oriented framework now in preview to enable AOT for ASP.NET workloads.
- neonsunset 3y ago
  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.
  - pjmlp 3y ago
    My experience with .NET goes back to the days MSFT sent CDs with documentation written in red only to select partners, while the rest of the world was unaware of Ext-VOS project outcome. The difference between us, is that my professional existence is not tied to praise .NET folks for everything they do. Everything that Microsoft ships on Visual Studio is part of .NET, without yes and buts.
    - neonsunset 3y ago
      This is the exact problem. It ails many very senior engineers - the circumstances have changed, but they continue on insisting it is still 2010 (in this particular case, closer to 2004). But hey, you were lucky enough for the problem to not cause significant issues, minor loss for the colleagues notwithstanding, good on you!
      - pjmlp 3y ago
        At least get .NET release date properly.

pjmlp 3y ago

The whole .NET 9 roadmap being driven by Aspire (works best on Azure) and Blazor. Stuff like minimal APIs driving C# features, e.g. lambda improvements required for replacing controllers with minimal APIs. There are hardly any desktop or COM improvements that are taken as seriously as the way the ASP.NET is. EF Core works best with Microsoft offerings, SQL Server, CosmoDB,.... The whole aspect oriented framework now in preview to enable AOT for ASP.NET workloads.

neonsunset 3y ago
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.
- pjmlp 3y ago
  My experience with .NET goes back to the days MSFT sent CDs with documentation written in red only to select partners, while the rest of the world was unaware of Ext-VOS project outcome. The difference between us, is that my professional existence is not tied to praise .NET folks for everything they do. Everything that Microsoft ships on Visual Studio is part of .NET, without yes and buts.
  - neonsunset 3y ago
    This is the exact problem. It ails many very senior engineers - the circumstances have changed, but they continue on insisting it is still 2010 (in this particular case, closer to 2004). But hey, you were lucky enough for the problem to not cause significant issues, minor loss for the colleagues notwithstanding, good on you!
    - pjmlp 3y ago
      At least get .NET release date properly.