The evolving infrastructure of .NET Core

Click for: original source

An article by Matt Mitchell in which he looks at the history of our infrastructure systems and the significant improvements that have been made in the last year or so in the world of the .NET Core 3.0.

The .NET Core project was a significant departure from traditional Microsoft projects:

  • Developed publicly on GitHub
  • Composed of isolated git repositories that integrate together vs. a monolithic repository.
  • Targets many platforms
  • Its components may ship in more than one ‘vehicle’ (e.g. Roslyn ships as a component of Visual Studio as well as the SDK)

The team working on the .NET Core early infrastructure decisions were made around necessity and expediency. The article explains then in some detail:

  • A three-pronged approach to development
    • Shared Tooling (aka Arcade)
    • System Consolidation (Azure DevOps)
    • Automated Dependency Flow and Discovery (Maestro)
  • Moving to Azure DevOps
  • Maestro and Dependency Flow
  • A Complex Graph

… you will get much more information in the article. The .NET Core evolved infrastructure quite a bit over the years. From Jenkins to Azure DevOps, from manual dependency flow to Maestro++, and from many tooling implementations to one, the changes they’ve made to ship .NET Core 3.0 are a huge step forward. Good read!

[Read More]

Tags agile programming azure devops