Net5.0 RC2: When building a solution with a target runtime ID an error is given
See original GitHub issueIn previous versions of dotnet core, you could build a solution with the runtime flag -r
and it would build for that target (ex. dotnet build -c Release -r win-x64
. Now however with RC2 it appears to echo out the error:
error NETSDK1134: Building a solution with a specific RuntimeIdentifier is not supported. If you would like to publish for a single RID, specifiy the RID at the individual project level instead.
If this is the new normal, is there a replacement method for cross-compiling an entire solution for multiple platforms?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:48
- Comments:36 (4 by maintainers)
Top Results From Across the Web
RuntimeIdentifier not available in dependent project when ...
Why is msbuild doing this and how can I pass the RuntimeIdentifier information to the DAL project when building/publishing the main project? ....
Read more >Azure Devops Build failing for .Net 5 when using multiple ...
I have a project that builds using the following frameworks: <TargetFrameworks>netstandard2.0;netstandard2.1;net5.0</TargetFrameworks>.
Read more >NET SDK error list - .NET CLI
This is a complete list of the errors that you might get from the .NET SDK while developing .NET apps. If more info...
Read more >Untitled
A runtime identifier must be specified in order to publish this project WebThe ... Net5.0 RC2: When building a solution with a target...
Read more >Fixing build warning NETSSDK1138 when ...
In this short post I describe how to get rid of the following build warning: C:\Program Files\dotnet\sdk\5.0.100\Sdks\Microsoft.NET.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop 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
Top GitHub Comments
Interestingly enough a
dotnet test MySolution.sln -c Release -r win-x64
works fine without any error. It also builds the whole solution with the specified runtime before executing all unit tests. How is that different fromdotnet build MySolution.sln -c Release -r win-x64
??? 😕Both should be possible.
This is especially confusing because
dotnet build --help
still lists this as an available option.Options should not be listed if they are no longer supported.