Convert repository to NuGet Central Package Management

[Copilot]

This PR converts the entire repository to use NuGet Central Package Management as requested in issue #7479. This centralizes all package version management in a single Directory.Packages.props file while ensuring the same packages and versions are restored.

Changes Made

Core Implementation

• Created Directory.Packages.props with 89 PackageVersion items organized by category:
  • Product dependencies (Apache.Arrow, Newtonsoft.Json, System.* packages, etc.)
  • Test-only dependencies (MSTest, XUnit, coverlet, etc.)
  • Build/infrastructure dependencies (MicroBuild, Arcade tools, etc.)
• Enabled ManagePackageVersionsCentrally=true property to activate central package management
• Removed Version attributes from all PackageReference items across:
  • 64 .csproj files
  • 4 .props/.targets files (test/Directory.Build.props, Directory.Build.targets, etc.)

Version Management

• All package versions use existing properties from eng/Versions.props (e.g., $(NewtonsoftJsonVersion), $(SystemCollectionsImmutableVersion))
• Maintains consistency with current version management approach
• No changes to actual package versions - only centralized the management

Package Resolution Validation

• ✅ Core projects restore successfully (Microsoft.ML.Core, Microsoft.ML.Data, Microsoft.ML.DataView)
• ✅ Test projects restore successfully (Microsoft.ML.Tests, Microsoft.ML.Core.Tests)
• ✅ Sample projects restore successfully (Microsoft.ML.Samples, Microsoft.ML.Samples.OneDal)
• ✅ Production projects restore successfully (Microsoft.ML.AutoML, Microsoft.ML.ImageAnalytics)
• ✅ Package versions resolve correctly (verified via project.assets.json files)

Benefits

1. Centralized Management: All package versions now managed in single location
2. Consistency: Eliminates version conflicts across projects
3. Maintainability: Easier to update package versions repository-wide
4. Transitive Pinning: Enables better control over transitive dependencies

Validation

The conversion was validated by:

• Individual project restore testing across core, test, and sample projects
• Verification that resolved package versions match expected versions from Versions.props
• Confirmation that no PackageReference Version attributes remain in project files

Note: Some GenAI projects have temporary restore failures due to network issues with JsonSchema.Net.Generation package from Azure DevOps feeds, but this is unrelated to the central package management conversion and will resolve when the feed is accessible.

Fixes #7479.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• dnceng.pkgs.visualstudio.com
  • Triggering command: dotnet restore Microsoft.ML.sln (dns block)
  • Triggering command: dotnet restore src/Microsoft.ML.GenAI.LLaMA/Microsoft.ML.GenAI.LLaMA.csproj (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[ericstj]

It looks like you might have missed helix.proj and codecoverage.proj. These files aren't built by the root build scripts. You can restore them with dotnet restore on the project itself. @copilot can you fix these up, please?

[Copilot]

It looks like you might have missed helix.proj and codecoverage.proj. These files aren't built by the root build scripts. You can restore them with dotnet restore on the project itself. @copilot ...

Fixed! I've converted both helix.proj and codecoverage.proj to use Central Package Management. Added the missing PackageVersion entries (Codecov, ReportGenerator, Microsoft.DotNet.Build.Tasks.Templating) to Directory.Packages.props and removed the Version attributes from their PackageReference items. (2174a03)

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• dnceng.pkgs.visualstudio.com
  • Triggering command: dotnet restore eng/helix.proj (dns block)
  • Triggering command: dotnet restore build/Codecoverage.proj (dns block)
• josvsblobprodcus372.vsblob.vsassets.io
  • Triggering command: dotnet restore eng/helix.proj (dns block)
• ljcvsblobprodcus317.vsblob.vsassets.io
  • Triggering command: dotnet restore build/Codecoverage.proj (dns block)
• vwvvsblobprodcus334.vsblob.vsassets.io
  • Triggering command: dotnet restore build/Codecoverage.proj (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• dnceng.pkgs.visualstudio.com
  • Triggering command: dotnet restore src/Microsoft.ML.GenAI.Core/Microsoft.ML.GenAI.Core.csproj (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• dnceng.pkgs.visualstudio.com
  • Triggering command: dotnet build tools-local/Microsoft.ML.AutoML.SourceGenerator/Microsoft.ML.AutoML.SourceGenerator.csproj --no-restore (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list

[tarekgh]

LGTM.

@ericstj left minor question regarding the removed references in the ns2.0 builds in the Microsoft.Data.Analysis.csproj. It looks build fine. I was just curious about it.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.99%. Comparing base (0708301) to head (24ee2e5).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7482   +/-   ##
=======================================
  Coverage   68.98%   68.99%           
=======================================
  Files        1482     1482           
  Lines      273880   273880           
  Branches    28254    28254           
=======================================
+ Hits       188943   188966   +23     
+ Misses      77550    77529   -21     
+ Partials     7387     7385    -2     

Flag	Coverage Δ
Debug	68.99% <ø> (+<0.01%)	⬆️
production	63.28% <ø> (+0.01%)	⬆️
test	89.45% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 4 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.