meta files don’t get updated and as a result the “referenced script is missing”). If you rename a class that derives from MonoBehaviour from within the IDE you usually break your project in Unity (the. I’m a maniac when it comes to naming so Ctrl+R is one of the most common shortcuts I use. Bam! Rename a class/file without breaking the. Autocomplete works even for non-imported assemblies and when you hit Enter, Rider automatically inserts the “using” statements into the appropriate place in your file. In Rider you can forget about all that hassle.
You suddenly remember you need to write “using UnityEngine.UI” or “using TMPro” at the top (import assemblies). If you’re using MonoDevelop the following will sound familiar: You want to reference Image or TextMeshProUGUI classes and your autocomplete does not cooperate with you. And here is why: Automatic inserts of “using” statements But many code inspections, intelligent variable naming proposals and Unity messages in Intellisense (no more copy-pasting of that OnCollisionEnter() from Unity docs!) made me put Visual Studio in front of MonoDevelop on my list within just a few hours.Īfter becoming almost a pro in going out of the comfort zone (“almost” being the keyword here), I was ready to try JetBrains Rider (there is 30 day free evaluation) to see if it’s worth the price tag.Ī few days later Rider became my number one choice for IDE. Well, it needs some manual tweaking to work ok with Unity (like this ProjectFileHook to suppress the constant CS0649 warning) and I had to reprogram some muscle memory because of how different the code completion works. I installed Visual Studio (for Mac) and used it for a few months. I decided was time to put the tip of my pinky a few centimeters outside the comfort zone.
Then, many projects later, came January of 2018 and Unity officially announced dropping future support for MonoDevelop. In the peak of my relationship with MonoDevelop (I call it a relationship because there were days when I spent much more time with it than with my wife.) a colleague told me about JetBrains Rider for Unity (back then it was still free), but I felt MonoDevelop did not slow me down so I said… “meh” and remained loyal. I’ve used it to code (and mess up too - see the side note at the end) quite a few projects. I’ve been using MonoDevelop from the very beginning of my adventure with Unity. Disclaimer 2: This is not an attempt at a comprehensive comparison of all available alternatives – simply a subjective description of my experience with Visual Studio for Mac and JetBrains Rider.
0 kommentar(er)
