<RuntimeIdentifiers> (plural) not supported in csproj
See original GitHub issueWhen building in Visual Studio I use the plural RuntimeIdentifiers to build for both x64 and arm64 for Maccatalyst, but I noticed that just makes .net meteor debugger doesn’t seem to interpret that, and instead does nothing.
<RuntimeIdentifiers>maccatalyst-x64;maccatalyst-arm64</RuntimeIdentifiers>
When I’m working on my project from my other computers with VS Code I have to swap it out and use <RuntimeIdentifier>maccatalyst-arm64</RuntimeIdentifier>
and just swap manually between arm64 and x64, which works, but it’d be really great if the plural was possible to use.
Issue Analytics
- State:
- Created 7 months ago
- Comments:13 (7 by maintainers)
Top Results From Across the Web
NET Core RuntimeIdentifier vs TargetFramework
NET Core because it's unsupported. ... <RuntimeIdentifier> (singular, not plural <RuntimeIdentifiers> ), otherwise you will get an error.
Read more >Support building for multiple RIDs, similar to how ...
if no RuntimeIdentifier (singular) is set in the project file, the build won't use any. Unlike the TargetFrameworks (plural), RuntimeIdentifiers ...
Read more >csproj settings in ASP.NET Core - kalapos.net
So the answer is yes, this is possible with the runtimeidentifier tag. Here is a .csproj file with this setting: Project Sdk="Microsoft.NET.Sdk" ...
Read more >EF Core fails to load hostpolicy.dll when RuntimeIdentifier is ...
I ran into another interesting one when working with a .NET Core 3.0 project and Entity Framework Core – this time, RuntimeIdentifier ......
Read more >.NET RuntimeIdentifier vs RuntimeIdentifiers - David Gardiner
A Runtime Identifier (RID) is used to identify target platforms where a .NET Core application runs. They come into play when packages ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
https://github.com/xamarin/xamarin-macios/issues/17707
Yep, I can reproduce this after killing a dotnet process. I will try to research this error…