PR Summary

This pull request refactors how the .NET SDK is installed in the build pipelines by introducing a new reusable template and updating all relevant pipeline templates to use it. It also updates the Install-Dotnet function to use a new download URL and cleans up legacy code paths. Additionally, it introduces a new pipeline parameter to control network isolation. These changes improve maintainability, consistency, and flexibility across the build system.

Pipeline .NET SDK Installation Refactor:

• Added a new reusable template install-dotnet.yml for installing the .NET SDK, replacing multiple direct usages of the UseDotNet@2 task across all major pipeline templates (linux.yml, mac.yml, nupkg.yml, release-validate-fxdpackages.yml, release-validate-globaltools.yml, release-validate-sdk.yml, testartifacts.yml, windows-hosted-build.yml, windows-package-build.yml, linux-package-build.yml). This centralizes and standardizes .NET installation logic. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]

• Updated scripts in windows-hosted-build.yml and windows-package-build.yml to explicitly call Find-Dotnet after .NET installation, ensuring the correct .NET executable is located before proceeding. [1] [2] [3]

Improvements to Install-Dotnet Script:

• Changed the Install-Dotnet function in build.psm1 to use the new download URL https://builds.dotnet.microsoft.com/dotnet/scripts/v1, and removed legacy code that handled different PowerShell environments, simplifying the function. [1] [2] [3]

Pipeline Flexibility and Parameters:

• Added a new parameter disableNetworkIsolation to .pipelines/PowerShell-Packages-Official.yml, allowing builds to optionally disable network isolation via pipeline configuration, and propagated this parameter through variables and template invocations. [1] [2] [3]

Other Pipeline Improvements:

• Updated the test artifacts pipeline to use new templates for setting version variables and cloning to the official path, further modularizing the pipeline. [1] [2]

PR Context

Allows the ability to use pre-release .NET SDKs

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge. If this PR is a work in progress, please open this as a Draft Pull Request and mark it as Ready to Review when it is ready to merge.
• Breaking changes
  • None
  • OR
  • Experimental feature(s) needed
    • Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed