Support for .NET SDK 7

I'm not sure how you needed MS Visual Studio to develop against net7.0 - not only have I written brand new things in net7.0 in Rider, I'm really close to a release on our main product which is an upgrade from net462 to net7.0 (asp.net mvc4 to asp.net core 7.0 mvc). At most, you could have disregarded the occasional warning and manually switched your toolchain.

Would it have been nice not to have? Sure. Was it a show-stopper? Not At All.

Dear Jetbrains, I have been using your products for a while (resharper v1). You are doing a great job! Release it when it is ready. I have done OSS stuff with Microsoft in the past and I am familiar with how the "sausage machine" works. Good decisions but it can rip through tooling like a living nightmare of a tidal wave for new major versions of the SDK. Suggest the "fast food culture raging" on this thread is kept to a minimum folks, you have no idea what a garganuation engineering feat it is to keep up with tooling for a major release of dotnet. Easy now, slowly slowly we will get there. Patience is a virtue my friends. #genx :)     

...isn't it obvious guys? The new tech-revolution started. Especially and maybe even foremost in our segment of the relevant industries (the stack of industries in which people do their work mostly at the computer and now face a lifechanging, potentially dangerous and a very hard to estimate future-prognosis , ...) Such a strong shift in the environments, workplaces and economies has never been here before. Since there is automatic programming, and that not being Closed Source,... Of course they have to focus on something else now. I cannot be mad at them at all. They have to pull all forces together or they could lose everything they've built up in all those past years (e.g. surpassing Microsoft in their alltime-leadership regarding C#/.NET/C  IDE-tools-of-the-hour). And ofc I am not talking about absolute numbers - many companies have a hard time changing their habits, so it's a slow process to reach the top - and an even harder to stay there when facing our present times. Their fast success and growth - not only vertically but also horizontally (number of languages, tools, employees, capabilities) just underlines this even more and also shows how much is at stake for them. You also should not forget how good JetBrains IDEs are in other non CLR-related areas. They are fighting many wars with many companies  - who all know how to implement the new AI stacks... All you have to see: JetBrains could lose everything right now. All they've built up for such a long time - in little to no time it could be gone due to exponentially growing AI-capabilities while their competitors in the very same industry,.. are most likely doing the very same thing right now - unless they're ... mhh not so clever. And that is: preparing your whole system for the big changes in order to be able to maintain the same quality in a diagonal and relative comparison with their competitors. I'm perfectly fine with not getting the fastest updates atm ... I rather prefer having a non-monopolist market with just a mediocre-to-good quality for some time instead of the JB-like quality that we all got used to - than the perfect supply in their darkest hours at the cost of risking their overall existance. Also you computer scientists and coders,... especially you should know how strong exponential growth/acceleration is. Being behind your competitor for just about 2 months of cumulative employee-working hours could mean to lose all their advantage in the industry soon.                          Greetings from somewhere 20km from CZ border, your fellow non-egoistic customer #2341171 who is grateful for the past years.

Love Rider but I have a project I need to collaborate on tomorrow so I really need this. Can't use Visual Studio on Linux. Do you have an expected shipping date for 7 support?

Thanks.

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

What is the correct channel to raise a concern for the current lack of progress from your side on .net 7 support?

.NET 7 was released today, hope Rider will be supported soon
https://devblogs.microsoft.com/dotnet/announcing-dotnet-7/

Keith Nicholas thanks, that makes sense.

When can we expect an update?

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

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

I also have the same issue reported by Craig

I downloaded the last version of the ReSharper CLI, tried to run it but I'm getting the error that .net 7.0 is not supported. Any idea when will be available a CLI version for .net 7.0? This is the message:

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

 Thanks!

Started to get worried after seeing that message "

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

"

I went all JetBrains in my dev environment recently and we do mainly .Net Core development.

I hope it's not true that .Net is a second rate citizen here at Jetrbrain

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 :)

Thanks Alexander Kurakin! Appreciate your time and work!

Since I can't seem to edit it, my previous comment was aimed at Pavel

Jesus man, we're looking at 2-3 weeks after the official release given it's in the latest EAP. Considering Jetbrains don't have the foresight or control MS have over the roadmap, that's really not that bad!

Stop being so bloody entitled, you're just embarassing yourself.

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.

Leandro funny - just compare it to current Rider status :-D https://youtrack.jetbrains.com/issues/RIDER?q=Type:%20Bug