5.0.100-alpha1-01483 SDK pulls down 3.0.0 preview 7 when netcoreapp3.0 tfm specified
See original GitHub issueWhen building with the nightly 5.0.100-alpha1-01483 SDK and targeting netcoreapp3.0, the SDK will pull down 3.0.0 Preview 7 bits instead of newer previews.
This was initially discovered in https://github.com/dotnet/coreclr/issues/26578
That issue also has an MSBuild binlog that shows the issue (the KnownFrameworkReference
for Microsoft.NETCore.App
for tfm netcoreapp3.0
has PackageVersion=3.0.0-preview7-27912-14
).
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
NETSDK1045: The current .NET SDK does not support ...
Go to Tools > Options > Environment > Preview Features, and make sure that Use previews of the .NET Core SDK is checked....
Read more >NET 5 cant be selected as Target Framework in VS2019 ...
I cant get Visual studio to use .NET 5. The following are my current configuration: Visual Studio Professional 2019 version: 16.7.6 .NET sdk: ......
Read more >NET Core 3.0.0 Preview 7 · Issue #3075 · dotnet/core
Please report any issues you find with 3.0.0 Preview 7, either responding to this issue, creating a new issue or creating a new...
Read more >Target Framework .Net Core 3.0 not available
We have determined that this issue is not a bug. In order for a released version of VS to work with a preview...
Read more >Calling Windows APIs in .NET5 - Windows Developer Blog
NET5 Preview 8, we have introduced a streamlined way for .NET developers to access the set of Windows Runtime (WinRT) APIs that are...
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 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
This is a known issue that will exist until 3.0 ships. We needed to pick an implicit version of 3.0 for 5.0 and at the time, P7 was the latest.
You can use global.json to pick a different SxS installed SDK. Sorry I was unclear on the other thread about that.
However, it is the case that .NET 5 SDK is not in great shape right now. The focus is on getting 3.0.101 and 3.1.100 out. These are shipping soon and have higher priority. Generally, you can always expect rough edges when using nightly builds instead of official previews, and in the very early days of a new major version, you can expect very rough edges.