Julietmikealpha

Edited October 02, 2026 13:40

Here are some logs (which, ironically, were stuck behind the scanning job).Upload id: 2026_10_02_9XgtiYxZDaCE7EXGMkh8Wb (file: rider-logs-20261002-14321811846106859581662741.zip)

1. Community
2. General Discussion
3. Rider.Net VERY slow at analysing project after upgrade to 2026.2.3 - chewed on my .net solution for 20 hours and it's not done

• 0 votes

Edited October 02, 2026 13:26

Actually, I guess I posted too soon - it is better, consumes less CPU (so the IDE is mostly usable) but is still ‘stuck’ scanning files in a large mono-repo. I've reverted back to a previous versio...

1. Community
2. General Discussion
3. Rider.Net VERY slow at analysing project after upgrade to 2026.2.3 - chewed on my .net solution for 20 hours and it's not done

• 0 votes

Edited October 01, 2026 16:48

There's a patch to Rider today that seems to have resolved this, testing a (new) Files view that was causing the IDE to slow.https://youtrack.jetbrains.com/articles/DOTNET-A-413/Rider-2026.2.3.1-re...

1. Community
2. General Discussion
3. Rider.Net VERY slow at analysing project after upgrade to 2026.2.3 - chewed on my .net solution for 20 hours and it's not done

• 0 votes