Why does Rider require a separate install of Mono for Unity projects?


I'm curious why I have to keep installing Mono stand-alone when working on Unity projects.  Why can't Rider use what Unity has?

It is kind of frustrating to have to set aside nearly 1gb for a stand-alone installation.  Further more, it concerns me that Rider isn't using the same assemblies as Unity will be using.

I LOVE Rider but it seems I frequently am having problems with the connective tissue between Unity and Rider.


EDIT After installing the stand-alone Mono I now still have the same problem.  I'm not sure what is going on.  Everything was working fine before I updated Rider :(

Rider 2018.3.4

Unity 2018.3.8f1

macOS 10.14.3 Mojave

11:39 .NET Framework Not Installed: MsBuild can not find TargetFramework assemblies, specify a Mono MSBuild in settings. You can download the latest stable Mono release.

Comment actions Permalink

Most likely, Rider has been using a .NET Core MSBuild, or failed to detect a Mono MSBuild. The solution is to set the Mono MSBuild manually via Preferences | Build, Execution, Deployment | Toolset and Build -> Use MSBuild version.

Comment actions Permalink

What if I am working on different projects in different versions of Unity? How do I make sure each project is pointing at the proper .NET for that Unity version?  Also how do I know which version to select in the first place for Unity? None of the items in the list seem to be obviously form a Unity install.

Comment actions Permalink

Hello @Juilia. I am having the same problem go @John but with not success to fix it.

It because it use that the MSBuild Version is set. Could you explain us why the error in detail.




Comment actions Permalink


To give you a proper reply I would need to have a bit more information: could you please send me the result of Help | Collect Troubleshooting information and Help | Compress logs and Show in Explorer. You can attach it here or add to a new issue. Thank you in advance!


Please sign in to leave a comment.