Apparently what this does is “For each player project, generate an additional .csproj file named ‘originalProjectName.Player.csproj’. This allows different project types to have their code included in Rider’s systems, such as assembly definitions or testing suites.”
I need to find a way to turn this off, because my VS is generating extra solutions (which are just duplicates) causing extra load times. I have another programmer on my team, using the same version of unity, and he does not have this problem. I am not using rider, and I do not want the .player extensions.
Even rider does not generate the .Players, which is supposed to be why they exist? Rider also seems 50% faster than VS on script creation/deleting compile times
However, adding Debug.Log(“”) statements do not print anything to editor.
For the one in AppData, if I do not specify UnityEngine.Debug.Log i get an ambigious warning when returning to the editor, but it still wont print anything.
I was finally able to find a solution thanks to JetBrains Rider support.
Install Rider
Install Rider in the Unity Package Manager
Select Rider under Preferences-> External Tools
If unity GUI shows a checkbox for “player projects”, then turn if off, regen proj files, and switch back to VS
***Stage 2 Issue
If Unity GUI doesnt show the player projects check box and packagemanager says rider is up to date, then unity packagemanager got rider stuck on an old version, you must manually fix this.
Navigate to root\Packages\manifest.json , then change “com.unity.ide.rider” to something like 3.0.7
**Stage 3 Issue
If upon reloading to Unity you get an error with rider in the package manager you need to uninstall nUnit either in the package manager, or remove the line in the manifest.json since rider seems to have some kind of dependency on it. Finally the option should appear to turn off player projects back under external tools.
It appears my VS2019 was using some old cached version of an EditorScript OnGUI that thought “player preferences” was serialized as “true”. For whatever reason VS2017 and actual Rider itself didnt think this.
My load times in VS2019 are now no longer a nightmare as its not generating duplicate .Player Solutions.