Whenever I download a new version of Rider, either EAP or mainline release, the experience of opening a solution in the new version is horrible.
During the process of re-scanning my solution, Rider will show thousands of false errors - right now I'm looking at 5242 errors in 318 files, and the number is rising. These are errors of the type "Cannot apply indexing to an expression of type 'System.Collections.Generic.List<Foo>" and so on - completely valid code that's being shown as not compiling.
Rider also pukes several dozen exceptions during the process, and it seems like most internal systems simply gets overloaded and breaks.
The result is that ever reinstall requires me to open the solution in Rider, allow it to do all of it's errors, close Rider, and open the solution again. That'll cause the errors to rapidly tick away until none are left, while Rider pukes another dozen exceptions.
Finally, I can restart Rider a final time and get back to working like normal.
This has been consistent for every Rider upgrade that's shipped. I was assuming that this was something that would get better over time, but it seems like it's not the case. Is it simply my project that's an outlier here, or is it just expected that Rider will utterly break when opening a large project for the first time?