Stride Game Studio crash on nugget dependencies change

[noncom]

Release Type: Official Release Version: 4.2.0.2381 Platform(s): Windows

Describe the bug

Just had the Stride Game Studio crash.

I was experimenting with some .NET libraries, and installed Microsoft.CodeAnalysis.Common 4.13.0 through Rider Nuggets manager.

On the next time opening the project both Rider and SGS showed me the error related to this (see the logs section).

Pressing Play in SGS was only repeating the error.

Since I have had already removed the libraries that required Microsoft.CodeAnalysis.Common 4.13.0 , I just removed this dependency in Rider nuggets manager as well.

Upon switching back to SGS it said it crashed and showed the crash report form.

I was unable to fill the crash report form becase after I wrote the first line of the message and pressed enter, all SGS windows, including the crash report form, closed.

I have no idea if it considered me pressing enter to mean sending the message, or if it just finally totally crashed, idk. But one thing for sure: pressing enter in the text editor should not send the form.

To Reproduce

I will just describe what I did, but maybe it doesn't have to be this specific.

Steps to reproduce the behavior:

0. Create and open the CSharpIntermediate sample project of Stride
1. Install the Infer.NET package
2. It requires the Microsoft.CodeAnalysis.Common 4.13.0 dependency, so I install it
3. Uninstall Infer.NET, the dependency remains.
4. Restart both Rider and SGS, see the error
5. Press Play in SGS once, see the error
6. Uninstall the nugget package of Microsoft.CodeAnalysis.Common 4.13.0
7. Go back to SGS and see the crash.

"Install" and "uninstall" means using the Rider nugget manager to add or remove the package.

Expected behavior No crash

Log and callstacks Added the logs. I also added some newlines into it for easier reading, since the original compiler message doesn't want to make it easy. package-version-conflict.txt

[Kryptos-FR]

Unfortunately, you can't use any other version than Microsoft.CodeAnalysis.CSharp 3.6.0 because of some dependencies that require this exact version. There is sadly no workaround for this at the moment.

Relates to #2124