Please welcome Rider 2019.2.2, which delivers about 60 fixed requests.
Here are the most significant fixes:
- .NET Core 3 Preview 8 support is available.
- A few more fixes in code completion.
- The performance of Solution Wide Error Analysis (SWEA) in ASP.NET projects has been improved. SWEA does not take ages to finish anymore!
- Lots of fixes in Razor support including resolving tag helpers and view-components, better formatting, and more.
- Android Layout Preview now works as expected.
- Code Analysis stops analyzing files and folders excluded from the analysis.
- The JavaScript debugger stops at breakpoints again.
Possible ways to get this hotfix:
- Download and install from www.jetbrains.com.
- Update right inside Rider: select Help | Check for updates.
- Use our Toolbox App.
- Use this snap package from the SnapCraft store if you are using a compatible Linux distro.
I’m not happy about new git window. It really makes me annoyed.
Please get back the git view without checkboxes.
Hey Max! Could you describe the problem in detail, please?
I agree on Max point, the new git window is not consistent with other JetBrain IDEs, I’m not sure why it get changed in Rider?
If we can get back the old git view that will be great.
Hi there, is the Entity Framework tooling updated to work with .NET Core 3.0 yet?
Here is a thread which actually makes integrating this in Rider urgent, since the command-line tools no longer work on .NET Core 3.0 so it is currently RELIANT on IDE integration for it to work. (https://github.com/aspnet/EntityFramework6/issues/1053)
Visual Studio has this implemented already but we’re on Mac/Rider exclusively, so it’s currently a blocker from moving over to .NET Core 3.0 – which itself has been a blocker for moving to Mac/Rider completely (we still run Windows VMs to be able to work on ANY changes to our models/DB)
Thanks guys!
UPDATE: The actual issue that enables integrating migrations into IDEs such as Rider is this one: https://github.com/aspnet/EntityFramework6/issues/231
Also please note your internal tag for prioritization for this is wrong (it’s marked as ‘nice to have’), but since on .NET Core 3.0 the command-line tooling NO LONGER WORKS, it’s blocking us from using Rider/Mac – or being forced to stay on .NET 2.2 and using side-by-side codebases running on Rider/Mac + Rider/Windows (extremely productive and slow).
Link for the mis-prioritized work item: https://youtrack.jetbrains.com/issue/RIDER-12403?_ga=2.159044474.1335242035.1567701638-1498817148.1534174900
It’s great to see a new version. I’ve been testing 2019.2.2 for the last week and seems to work. No problem with new git screens but was confusing the first time.
What seems really annoying it’s that the editor freezes too often. Even hitting tab key to increase space produce a notice that Rider is doing something and will do it once it finish. (I can’t remember the exact message). I think that its related to a couple of things. My computer is a windows 7 with 8gb ram and a little bit old cpu. The second reason might be that Rider is inspecting my code and this is awesome in the way helps writing better code but in the other hand, going so deep in inspections make it so slow that I will change the IDE. ( I won’t change my computer right now).
Even though, I love Rider and I will use it in the future once this freezing stops bothering me.
Hello Martin,
I’m sorry for the inconvenience.
I would ask you to collect the following information and share it via creating a new support request (https://rider-support.jetbrains.com/hc/en-us/requests/new?ticket_form_id=97145):
1. Enable the trace scenario for SWEA in “Help | Trace Scenarios (LOGS)”
2. Collect a backend performance snapshot according to the “Embedded profiler” section of the article https://rider-support.jetbrains.com/hc/en-us/articles/207490549-Rider-Profiling-Instructions-NET-process-
3. Collect all Rider logs via “Help | Compress Logs and Show in …”
4. Disable tracing in “Help | Trace Scenarios (LOGS)”
5. Share all collected data (how to share is described here https://rider-support.jetbrains.com/hc/en-us/articles/208199755)
As a temporary workaround, you can try disabling solution analysis in “Editor | Inspection Settings” -> “Enable solution-wide analysis.” Alternatively, you can download the previous working version from https://www.jetbrains.com/rider/download/other.html>
Has this issue been created? I have the same problem. Rider is unusable if not in power save mode.
Hi ,
I have updated to 2019.2.2 for mac, but when I open, IDE displays a blank screen. I am not able to see any tool windows (Project Explorer, Terminal etc… including toolbar) I cannot even get them by selecting from Tools Menu. Apart from tool windows, I am not able to open any file by selecting double shift (quick open). This has happened with me for Datagrip too a month back. So I had to reinstall older one. Is there some problem with machine?
I tried, Invalidating Cache, reset settings, and re-installing 2019.2.2. Nothing works… I think I’ll stick to 2019.1.
Hello,
This problem seems to be a known one https://github.com/ChrisRM/material-theme-jetbrains/issues/1282.
Could you please clarify if you use Material UI? Would it be possible to disable the Material UI plugin and restart the IDE? Does the problem persist?
Hi,
Thanks for pointing out to issue. I am using Material theme. After Update, to make windows visible, I have moved main window around as stated here https://github.com/ChrisRM/material-theme-jetbrains/issues/1282#issuecomment-527010976. Later on I have updated Material theme plugin and now it works fine.. I think, it would be better if Plugins are updated along with IDE…
Hi Seshagiri,
Thank you for the information.
Downloaded plugins are updated automatically during the Rider update via Toolbox (https://www.jetbrains.com/toolbox-app/).
Hi,
we are developing Windows Forms .NET Framework Applications using VB (Visual Basic). The Windows Forms Editor only seems to work for C# projects. Why?
Greetings,
flo
Hello Florian! There is a separate feature request on YouTrack https://youtrack.jetbrains.com/issue/RIDER-25091 to support VB.NET. Feel free to vote for it.
Hi,
VisualBasic WinForms functionality has not been supported yet. Please upvote the feature request: https://youtrack.jetbrains.com/issue/RIDER-25091.