|
We upgraded an existing project from Unity 3.4 to 3.5. Ever since, the 'Find References' functionality in MonoDevelop seems to be incredibly slow. In fact, it's so slow in our codebase (which is pretty large) that it's unusable. I rely on it extremely often since doing normal string searches (e.g. Find in Files) isn't good enough given the size of our codebase and the similarity of our function and variable names across multiple classes. Is there anything I can do to speed this up? If not, can I roll back the version of Monodevelop to the one from 3.4? Can I use a non-customized version of MonoDevelop (where this bug has been fixed) with Unity projects?
(comments are locked)
|
|
I was able to setup unity to use an older version of Monodevelop-Unity (from 3.4) that I still had installed beside the 3.5.1 version. I went into the 'Preferences' menu for unity, and set the 'External Script Editor' to the version of MonoDevelop from within the old Unity installation. This seems to be working for me. Good workaround. That was driving me up a wall.
Jun 29 '12 at 10:16 PM
Geoff
Yes, except the old version of MonoDevelop is unable to attach and debug to the current version of Unity, so I'm stuck doing everything with prints. I kept hoping that they would fix this issue in a point-release, but it's up to 3.5.4 and it doesn't look like they care at all. :(
Aug 02 '12 at 02:00 PM
AntonStruyk
(comments are locked)
|
