I´m not sure where to post this but it seems like MonoDevelop would sorta become Unity´s >official< suggested Coding Tool with Unity 3 so i gave it a try now for some days and well, i´m really trying to like it but its making it really difficult for me to like it =( =)
So i thought maybe people could post their views on it and maybe we can forward it as group feedback then.
So some things i dislike so far:
-The options for search seem to reset themselves regularly (like let´s say i set it to Case insensitive search, after a while its set back to Case sensitive),very annoying
-There seems to be no hotkey combination for search and replace
-There seems to be no autocompletion for unity js stuff for runtime created stuff
-The autocompletion has no good hitrate in general with its suggestions and i´d much prefer it if the suggested word was only set if i press enter, not having to force not selecting it by pressing esc etc, again very annoying when one gets a wrong word added
-The coloring of different things is awful and very unintuitive, why are for example comments colored in jump in your face blue and numbers in pink?
You should post such stuff on the monodevelop related environments so the monodev developers know about it. naturally after checking the already reported bugs etc
posting here makes no difference cause monodevelop is the only option available for debugging mono at all, that simple it is
I’d be happy if the version of Monodevelop they supplied actually worked at all in my copy of Win7. I’m surprised they didn’t supply an msi rather than a zip.
Instead I’ve just downloaded the version from the monodevelop website itself. It’s considerably lighter, it probably wont work fully with Unity, but at least it runs.
to dreamora:
yeah, i thought of posting there right away but i first wanted to get the view of some others using it for unity stuff and also felt like a unitied voice of the unity developers could maybe lead to more than a single guy asking for changes =)
Thats naturally true that if more than one person requests it towards the monodevelop team it might get more weight.
@Per: the gain of an msi would go somewhere towards 0. From what mentioned from others you need to install GTK# (gtk for windows) though. Can’t comment on that as I use U3 right now only in its iphone version and thus on osx where monodevelop just works (and just crashes whenever it feels like it )
and no the one from monodevelop will not work at all with unity
Unfortunately it’s not the lack of the latest GTK# unless there’s also a unity version of that not listed in any download, i’m just using the version specified on the MonoDevelop page (2.12.9)
The unhandled exception error I get is:
System.InvalidCastException: Unable to cast object of type 'System.WeakReference' to type 'Mono.Addins.ExtensionContext'.
at Mono.Addins.ExtensionContext.ResetCachedData()
at Mono.Addins.AddinSessionService.ResetCachedData()
at Mono.Addins.Database.AddinDatabase.ResetCachedData()
at Mono.Addins.Database.AddinDatabase.Update(IProgressStatus monitor, String domain)
at Mono.Addins.Database.AddinDatabase.Repair(IProgressStatus monitor, String domain)
at Mono.Addins.AddinRegistry.Rebuild(IProgressStatus monitor)
at MonoDevelop.Startup.MonoDevelopMain.Main(String[] args) in c:\BuildAgent\work\c4f9b244eafc8245\monodevelop\main\src\core\MonoDevelop.Startup\MonoDevelop.Startup\MonoDevelopMain.cs:line 28
There is no c:\BuildAgent path on my machine, does anyone know what should be there?
The gain of an MSI would be somewhat towards a great deal. On OSX Monodevelop is a package, in Windows, it’s a large zip file containing numerous branches, application files, libraries and helpers, though sadly no installer or indication of suitable location (one has to assume it’s a 32bit program and the whole folder should go in the x86 program folder, not in the unity project folder or any other arbitrary location, considering it sets up no environmental variables). So yes on OSX an installer does nothing, but on windows it would actually be rather convenient.
Well I’ve got it working, for those interested you need to remove all the duplicate dll’s in the assets folder, that were apparently accidentally added in to the zip last time around (according to UT).
The one downside I seem to have here is that every time I click on anything in unity to open it in MonoDevelop it doesn’t open as part of the project, but instead in a totally new MonoDevelop instance. So of course you get no autocomplete. Visual Studio 2010 was a bit better behaved with this regards and Unity 2.6
)