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
|
<PackAsToolShimRuntimeIdentifiers>win-x64;win-x86;osx-x64</PackAsToolShimRuntimeIdentifiers> |
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.
Is your feature request related to a problem? Please describe.
I am trying to run the
libmanCLI 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-arm64was added to the PackAsToolShimRuntimeIdentifiers tag inLibraryManager/src/libman/libman.csproj
Line 8 in b0570cd
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.