Support for the Upcoming .NET SDK 7

The latest Rider 2022.3 EAP builds support .NET 7 SDK. Please download them from https://www.jetbrains.com/rider/nextversion/

43 comments
Comment actions Permalink

Srsly? Like, SERIOUSLY??? .Net 7 is in 2nd RC - not preview, about a month before official release (in fact, if we were to consider previous release dates - Nov 10 for #5 and Nov 8 for #6, likely less than a month, probably on the .Net conference Nov 8-10). RC means "supported for production workloads." What does "closer to release" mean, exactly? These are exactly the reasons why I'm considering not renewing my jetbrains subscription this year.

Edited by Pavel
33
Comment actions Permalink

Give them a break. JetBrains is a great company and Rider is the best IDE.
We don't know what is involved in supporting .NET 7 in such a complex code base, and JetBrains has an EAP with support.
Stop being so entitled and rude. This isn't worth an emotional outburst.

9
Comment actions Permalink

Gotta love when people like your product so much they get a bit angry at the prospect of not being able to use it.   I'm using .NET 7 in Rider EAP 6.  Also, the new UI ( which you have to turn on ) is really good! Good job guys

8
Comment actions Permalink

Ben van der Stouwe this post keeps changing, it said quite different things before, such as Rider doesn't support .NET 7 and they weren't going to support it until things settle (this is while it was RC and "Go Live" ).   Then we started getting builds that hard partial support.   However, some people are a little dramatic, and mostly Jetbrains has been pretty quick with support in the past, so not sure why people were worried.

8
Comment actions Permalink

Dear everyone! 

Here is a small update about this matter: 

  • The ".NET SDK 7 is not fully supported" message was removed in the 2022.3 EAP8 build
  • We are going to deliver two more EAP builds before the final release to polish all the things. 
  • We are going to release Rider/ReSharper/.NET tools 2022.3 at the beginning of December. 

Thanks!

7
Comment actions Permalink

Source generators don't work when using NET 7 RC2 MSBuild.

7
Comment actions Permalink

"(right now .NET 7 itself has many issues to fix)". I see 15 open and 5.4k+ closed. Please update the post so at least it makes more sense. People are watching it. Good communication is the least I would expect for being an Ultimate subscriber.

6
Comment actions Permalink

Anyone else finds the lack of reaction from Jetbrain's side to be mildly irritating?

6
Comment actions Permalink

James Hughes James:

  • The original comment is from October. At that time, .Net 7 was in RC2 and the post from Jetbrains (which has now been changed) said something along the lines of ".Net has itself many issues, we'll look into it closer to its release" - which at that point was less than a month before the release
  • For previous releases - .Net 5 and 6 (can't tell for .net3 as there was no Rider back then), Jetbrains had official EAP with support for the upcoming .Net in (if I recall correctly) in August or September. For .Net 7, less than a month before official release, it said "we'll look into this later". WTH?
  • I have been paying for the all products subscription since whenever it came along (and have been a paying Jetbrains customer for about 10 years now - myself, not an employer or something like that), so I can compare both over time service degradation as well as the development speed among different Jetbrains IDEs. In general, the features are available in IntelliJ, then the rest, and then long time after in Rider. Goland always has up to date feature set with both official and pre-release of Go, for instance. Same with Java. Rider on the other hand is often a year or more late with features that other Jetbrains IDEs have (such as container development, Code with me etc.)
  • .Net development is very transparent, and roadmap has been stable since January and first preview came out in mid February. That is a lot of time. .Net development is not a MS blackbox, hasn't been for many years now.
  • You're confusing entitlement and customer service. If I'm paying a subscription, I expect the service. And the service has degraded greatly comparing to what it was before. Or, in another words, I paid for a different level of service (based on previous experience) at the time of subscription than what I'm getting right now. And if that still sounds too cryptical for you: If you go to a pub for 10 years, always order Heineken and always get Heineken, and then suddenly one day order Heineken again but get PBR for the same price without any explanation, it's not entitlement to call it out.
  • The fact that the original post has changed several times by Jetbrains in the past few weeks and now my original comment seems less relevant is unfortunate, but considering nobody from Jetbrains made any comment or response to this thread and instead changed the post is by itself wrong and shows a rather strange approach of Jetbrains towards its longtime paying customers. I haven't seen this kind of communication from a reputable company in quite a while.
  • So, to paraphrase your own words, shut your bloody mouth, you have no idea what you're talking about.
5
Comment actions Permalink

.NET 7 released today, hope it would be supported soon

Edited by Li Weihan
4
Comment actions Permalink

Is EAP7 considered to be last EAP? I.e, are you sync with .NET7 SDK official release date? Or any estimates to final release?

4
Comment actions Permalink

I downloaded yesterday, but it simply didn't work. It opens the 1st screen to select the projects, I choose one and then it just closes Rider and comes back to the 1st screen... For now, I will have to stick with VS which last update is fully supporting .NET 7

3
Comment actions Permalink

Can't wait. Keep up the good work :)

3
Comment actions Permalink

I don't understand the problem. I just migrated our projects from dotnet 6 to dotnet 7 (#dropthedot) and everything works fine in Rider Release 2022.2.4. Stuff like the `required` modifier are recognized. Sure I'd like Rider to autofix the possible null value warnings with the `required` modifier instead of ` = null!` insert, is that's what this issue is about?

3
Comment actions Permalink

Quite a few peeps here should chillax. Rider 2022.3 EAP 8 has a wonderful support for .Net 7 and the new UI is fast and pleasant to work with. Nice job, JetBrains. Keep up the good work.

 

Running on macOS. 

Edited by Dydek
2
Comment actions Permalink

Just started a new project and wanted to use .NET 7 as it's in RC and Microsoft supports it for production, but because of Rider not supporting it, I'm forced to use Visual Studio.... :(

1
Comment actions Permalink

Good to hear it @Dydek but all I get when I open a dotnet  7 project in Rider 2022.2.4 on Linux MInt 21.0 is the following:-

I guess the sooner 2022.3 EAP 8 makes it into production the better ;)
Do you know when that will be, by any chance?

Edited by Craig
1
Comment actions Permalink

When can we expect an update?

1
Comment actions Permalink

Can you please provide a timeline of when new tech will be fully supported. MAUI and Blazor etc.

1
Comment actions Permalink

Thanks, Alexander Kurakin! Looking forward to it and appreciate the hard work and time on this matter!

0
Comment actions Permalink

Well - I'm not sure what's happening in Jetbrains lately, but the .Net ecosystem just seems to slip into 2nd class citizen category. In Rider, Remote/Container took super-forewer to become available and is buggy as f/k, no code with me support, Resharper seems to be slower with every release, despite computers being faster... and less than a month before major release, the only support message on it is that Jetbrains will start looking into it closer to the release. That's like the poster child of WTFs.

Edited by Pavel
0
Comment actions Permalink

Pavel better take a look at a new UI and black-screen Rider freezes after a while ;)

0
Comment actions Permalink

Salvador C Repasa Just note that was for resharper rather than Rider.   Not sure what is happening in the resharper world, left that a long time ago :)

0
Comment actions Permalink

Thanks Alexander Kurakin! Appreciate your time and work!

0
Comment actions Permalink

Im experiencing same issue with EAP7 same as André Miranda

 

I downloaded yesterday, but it simply didn't work. It opens the 1st screen to select the projects, I choose one and then it just closes Rider and comes back to the 1st screen... For now, I will have to stick with VS which last update is fully supporting .NET 7

 

Reported as https://youtrack.jetbrains.com/issue/DEXP-695243/Assertion-failed

Edited by Syedhoque89
0
Comment actions Permalink

I also have the same issue reported by Craig

0
Comment actions Permalink

Have you tried invalidating caches and restarting (from the file menu)? I've had some times when an upgrade to rider doesn't play nicely with existing project caches.

0
Comment actions Permalink

Hi all,

I was able to resolve the issue "The current .NET SDK does not support targeting .NET 7.0". I don't know if this is specific to Rider.

MSBuild 17.4 is required for .NET 7. For some reason, even if you have SDK 7.x installed, the build tries to use older version that only works for .net 6.

Add a global.json file to the project to tell MSBuild the SDK version to use. For example (not sure if you have to be so specific with the version, looks like "7.0" works as well):

{
"sdk": {
"version": "7.0.101",
"rollForward": "latestFeature"
}
}

find your latest sdk version installed with > dotnet --list-sdks

Edited by RLU
0
Comment actions Permalink

If you're seeing

The current .NET SDK does not support targeting .NET 7.0 

then try switching your tooling (settings -> build, execution, deployment -> toolset and build -> msbuild version). What I've found is that using msbuild from vs2022 _Community_, all up-to-date, produces this error, but using msbuild from vs2022 _Build Tools_ (all up to date) works just fine. For me, the Rider warning is just that - a warning - I'm currently working on many solutions targeting dotnet7, in Rider. I came here to find out _what_ isn't supported, and that hasn't really become apparent. Apart from the warning, after ensuring that I'm using _Build Tools_ and _not_ VS proper, I wouldn't even know the difference from targeting net6.0.

 

Interestingly, some projects seemed to be easily upgraded from net6.0 to net7.0 without any issue, and other times I had to manually set the build tools msbuild for use. I only have vs2022 community installed "just in case" I need an IDE - I tend to use Build Tools anyway, rather than the built-in msbuild, because I can update it out-of-band and I have CLI build for all my projects anyway, so I'm going to need CLI tools.

0

Please sign in to leave a comment.

Have more questions?

Submit a request