Support for the Upcoming .NET SDK 5.0

Microsoft recently published the first preview for the upcoming .NET SDK 5.0. Rider does not yet provide official support for the newest SDK. Before we run the full QA cycle to identify all the situations where Rider behaves incorrectly, we’re going to wait for more stable bits of the SDK (right now .NET 5 itself has many issues to fix). We will get Rider fully tested on .NET SDK 5.0 closer to the .NET SDK 5.0 release.

If you’ve noticed any other problems which you think might be related to the installed .NET SDK 5.0-preview, please keep in mind that it might be a current limitation of .NET SDK or simply a bug in the preview. If you still think it is a Rider issue, please file a new issue on YouTrack and explicitly mention that the preview SDK is installed.

We plan to provide full support for .NET SDK 5.0 in Rider 2020.3 release later this year.

13 comments
Comment actions Permalink

Is Rider 2020.1 EAP7 a typo? As we're on 2020.2 EAP8 now.

0
Comment actions Permalink

Looks like RC1 is up, and I note that this article was updated today. Are there any more specifics on the 5.0 support timeline now that we have a RC? I'm most concerned with the upgrade path. Will there be a straightforward migration for projects? I'm starting a new project now and want to make the best choices.

Edited by Zaneclaes
2
Comment actions Permalink

Is there an EAP with 5.0 support? 

1
Comment actions Permalink

As above, we're only two months from the release and there is an RC candidate available so how can we get this tested within Rider?

I've installed the RC1 SDK and Rider detects the new msbuild, and I can set the project to C#9 and it builds. But there doesn't seem to be any support for the new C#9 features.

0
Comment actions Permalink

Hello everyone! 

The first EAP build of Rider 2020.3 will have initial support of .NET 5, including:

  • The first steps in C# 9 support: Top-level statements, native ints, target typed conditional expressions, static lambdas, and DynamicallyAccessedMembers attribute. 
  • Support for the new way in the NuGet restore.
  • Coverage and performance profiling work with the new SDK.
  • etc.

We are planning to open EAP this or next week. So, stay tuned!

Thanks! 

3
Comment actions Permalink

Great! Thanks for the update :D

0
Comment actions Permalink

looking forward to trying it out.  I want to upgrade a project from 3.0 to 5.0

0
Comment actions Permalink

Using the latest EAP Rider (Build #RD-203.4203.15, built on October 1, 2020)
I am getting the below errors when trying to build my solution:

```
Microsoft.PackageDependencyResolution.targets(234, 5): [NETSDK1005] Assets file ....\obj\project.assets.json' doesn't have a target for '.NETFramework,Version=v5.0'. Ensure that restore has run and that you have included 'net50' in the TargetFrameworks for your project.
```

The same exact solution builds and runs OK with VS 2019 Preview
Is there anything that can be done?



1
Comment actions Permalink

I'm getting that too, I have to manually restore my projects (dotnet restore) before building or having resharper not show a slew of errors.

The new project window also incorrectly shows.NET Framework sdk targets for the templates when using the .NET 5 sdk (e.g. ".Net Framework v4.7.2"), something along the chain incorrectly identifies TargetFramework net5.0 as a .NET Framework identifier.

1
Comment actions Permalink

Danielle thanks for the report! 

Please file a new issue here https://youtrack.jetbrains.com/issues/RIDER and attach log files (`Help | Collect Logs`) right after you get the error. 

Thanks! 

0
Comment actions Permalink

corrupt Thanks for the report! You told "ReSharper", are you sure? ReSharper uses Visual Studio to restore packages. Thanks! 

0
Comment actions Permalink

I misspoke, I meant Rider just ends up showing a lot of red because types are missing as .NET Framework 5.0 (which isn't a thing) assemblies can't be found.

0

Please sign in to leave a comment.

Have more questions?

Submit a request