ARM64EC/ARM64X support for apphost, allowing one apphost to launch either x64 or ARM64 runtime
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- build-system
Research direction
Start with dotnet/sdk#26647 and the referenced comment, then trace the dotnet publish path for framework-dependent apphost generation. The issue names no source files or tests; done means producing one AnyCPU executable that launches natively on x64 and ARM64, with validation points identified during investigation.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
dotnet/sdk#26647 highlights an important shortcoming in .NET: the inability to publish for AnyCPU. With the recent push for Windows on Arm, I think it's important to have an officially supported way of shipping AnyCPU executables. It's silly if .NET Framework can do it just fine, but the supposedly better, more modern version cannot.
There is some discussion there about the technical challenges for 32-bit x86, but I'd like to re-contextualize this issue to x64/ARM64, which is arguably more important for the future of the Windows ecosystem. The original issue has been untriaged for 3 years.
Describe the solution you'd like
Being able to dotnet publish a (framework-dependent) AnyCPU .exe file that runs natively on x64 and ARM64, ideally x86, too. How it's implemented behind the scenes or what PE headers it has is not important.
Additional context
Relying on dotnet myapp.dll doesn't play nice with tools that make decisions based on the .exe, such as Xbox Game Bar, GPU drivers, some application firewalls; the issue highlighted by this comment; and I'm sure many others.
- Dominant language
- C#
- Stars
- 18.3k
- Forks
- 5.6k
- PR merge metrics
- PR metrics pending
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/runtime
-
agentic-workflows untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
area-System.Reflection blocking-clean-ci-optional Known Build Error os-mac-os-x untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
area-CodeGen-coreclr untriaged
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
agentic-workflows untriaged
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
area-VM-meta-mono untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·
-
area/docs-content Bug pulumi/docs
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
-
Create parent directories only after the containment check in InstallHelper.TryExtractToDirectory Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PowerShell/PSResourceGet#2056 ·