I contemplated putting this in one of the 20 MonoDevelop topics, but I’m more or less faced with a lot of issues on just about anything I’m plugging into Unity for scripting. So really, I could use just about anything that would work.
The gyst is that I’ve been trying to get any IDE to work as they should with Unity 2017.3 and they do very much not work. My main two candidates for “please let me do my work” editors are MonoDevelop and VSCode. I’m fine with either, but both have been problematic.
My preference would be to keep using MonoDevelop, as it’s simple, clean, and got the job done for me. But I’m pretty sure I did something so horrible that MonoDevelop won’t even speak to me now. I followed the various guides and workarounds that have been posted across multiple topics here to no avail each time. The initial problem I had was the classic “open one script and Unity keeps opening MonoDevelop” which ultimately degenerated into “MonoDevelop doesn’t open at all as a program anywhere” after going with some repo somewhere with it. Yes, I installed mono-complete and all that stuff. No, I have no idea what to do now.
VSCode opens the solution and anything I open in the editor fine, but lacks any form of autocomplete or intellisense outside of type names. C# and some Unity extensions are on, and it seems to load the solution just fine until it starts complaining about CLI. I’ve installed CLI in a previous attempt to use VSCode on Linux and having seen it has done absolutely nothing to fix this reoccuring issue, I find it’s not worth wasting my time downloading a dev tool, registering an account to it, and disabling its telementary. I don’t know if it’s related to that, since before it’s failed to do anything, but I typically got this warning when trying to load this solution:
Background: I recently just installed Linux Mint 18.3 XFCE, coming from 18.2 KDE and having been using Unity Linux for a long while now on different levels of Mint. I say this because I want to assure that I’m aware this is all beta stuff and that it’s a really appreciateable effort to have a native Linux build at all. I’m pretty happy that I get to work on my preferred OS at the capacity this currently supports. This should be established so my complete and utter frustration over this issue isn’t seen as just tearing down and trivializing what all the Linux team is doing. With that out of the way, I’m not very remorseful on setting fire to some really obnoxious issues that has so far costed me two days in productivity (and it will get worse if I don’t just go ask for direction here and now) because of 2017.3’s lack of baseline support for an IDE.
Concludings: Pardon that this probably sounds really complainy. I was gaining a lot of progress across the last week or so, and this problem smashed me into a brick wall where I have not been able to accomplish anything. It is very, very frustrating and I will probably have to drag all my stuff to Windows until someone here can give me some kind of guidance to help fix this disaster.