Skip to content

Establish the .NET 10 build baseline - #2

Closed
atcarter714 wants to merge 1 commit into
mainfrom
migration/net10-build-baseline
Closed

atcarter714 wants to merge 1 commit into
mainfrom
migration/net10-build-baseline

Conversation

@atcarter714

@atcarter714 atcarter714 commented Nov 4, 2026 •

Copy link
Copy Markdown
Owner

The experimental solution now targets .NET 10/C# 14 with a pinned SDK, central package versions, committed dependency locks, and SDK-style build imports that also work for individual projects. Adds a PowerShell build entry point and Windows Debug/Release CI covering a small non-GPU test group, packing, and an isolated package-consumer build.

Repairs existing compilation blockers and solution configuration mappings, removes duplicate native package references and startup-script dependencies, and updates native build inputs to retail Agility/DXC. The existing CsWin32/metadata projection is deliberately frozen until the generated-COM qualification step. The README's architectural self-assessment is preserved.

Validation: both Debug and Release restore/build/pack/package-consumer checks passed locally with SDK 10.0.403 on Linux using explicit -SkipTests. PowerShell, XML/JSON parsing, and git diff checks passed. Windows test execution is delegated to the new CI and has not been claimed as passing. Existing warnings remain visible.

This PR establishes the build baseline. Generated COM ownership, native ABI qualification, runtime bootstrap/native package deployment, completed DXC/DirectML support, and sample runtime qualification remain subsequent migration work. See doc/NET10-Build-Baseline.md for commands, test boundaries, and recorded starting failures.

Consolidated by the preview 1 release in #9 and retained in main through #31. Verification: this PR head is an ancestor of release/automation at 1ba30ff4a36b6c4a7f8a31f342599026178c2cd0, whose tree 1c2649258445a6a22abeaa58cbc139c9384d0c5f exactly matches released main commit 0dcb5e3fbb984c23a1f313c87ec72ea0cbfe5fc4. Follow-up SDK work is tracked in #32–#35.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant