Add macOS Arm64 support to the CLI tool

Open

#708 opened on Mar 2, 2023 4 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 1/5
Estimated time: 1-3 hours
Newbie friendliness: 55/100

Issue type: Feature
Clarity: Clearly specified
Activity status: Stale
Tech stack: csharp
Domain: cli

Research direction

Inspect src/libman/libman.csproj at the PackAsToolShimRuntimeIdentifiers tag and compare the requested osx-arm64 RID with the linked .NET RID catalog. Update the project configuration so the CLI supports macOS Arm64, then verify that the packaged tool can run with an Arm64 .NET runtime.

Written by the indexing model from the issue text.

Description

Is your feature request related to a problem? Please describe.

I am trying to run the libman CLI tool on my Mac mini M2 Pro after installing the recommended Arm64 versions of the .NET SDK, but it fails and says that it can't find a .NET Runtime.

Describe the solution you'd like

Correct me if I'm wrong, but I think the problem could be solved if osx-arm64 was added to the PackAsToolShimRuntimeIdentifiers tag in https://github.com/aspnet/LibraryManager/blob/b0570cd92d4c7e8c4650a3ebbb76838eec069469/src/libman/libman.csproj#L8

I saw a lot of macOS RIDs here and none of them were specifically "osx-arm64", but they do have "osx.13-arm64", so you'd think they'd have a non-version-specific one.

Describe alternatives you've considered

I solved the issue momentarily by installing the x64 version of the Runtime, but I read that running that version uses an Intel emulator and I'm wondering if there's overhead there.

Dominant language: C#
Stars: 486
Forks: 91
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing 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.

Similar issues

CS0162 "Unreachable code detected" warning from a MSBuildTemp .tmp file in every game project Open

bug

Difficulty 1/5 Under an hour Newbie friendliness 90/100

stride3d/stride#3477 · Opened Sep 23, 2026
docs: update contribution guidelines to account for AI-generated contributions Open

Type: enhancement

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

apache/arrow-adbc#4809 · Opened Sep 23, 2026
[quality-improver] CiRunSummaryAggregateReader.ValidateModule provenance cross-check guards are untested on the throwing path Open

type/automation type/tech-debt

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

microsoft/testfx#11477 · Opened Sep 23, 2026
.NET 11 isolated: feed entries using the new `Azure.Functions.Sdk` MSBuild SDK are misdetected as in-process, so no templates are found Open

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

microsoft/vscode-azurefunctions#5197 · 1 comment · Opened Sep 23, 2026
reactor-build-and-check says mur is 'selfhost only', but mur.exe ships in the same skill-kit zip as that skill Open

Difficulty 1/5 Under an hour Newbie friendliness 85/100

microsoft/microsoft-ui-reactor#1274 · Opened Sep 23, 2026

More C# issues