4 ms·
I'm running it in prod since last year and from the runtime perspective there are no issues. Tooling is what sucks. MonoDevelop F# support is very unreliable.
by insulanian 10y ago
I'm running it in prod since last year and from the runtime perspective there are no issues.
Tooling is what sucks. MonoDevelop F# support is very unreliable. Basic refactoring, like rename, don't work correctly every time and I had to literally do git reset few times, after renaming, as it screw up multiple files.
Also, editor often has visual glitches where letters get corrupted and I have to reopen the file to get it back to normal. Not something I expect from such a long time maintained application.
However, it looks like Xamarin Studio 6.0 will be much better.
Alternative is Visual Studio Code with Ionide plugin, but I didn't use that beyond trying it once. Hopefully someone else can comment.
Edit: typos
- 7sharp9 10y agoXamarin Studio and MonoDevelop are the same, what your probably seeing are the artefacts or using an old version of MonoDevelop
- insulanian 10y agoI'm using the latest stable release of MonoDevelop (5.10)
- sremani 10y agoThe latest if you pull from github is 6.1 (I think), using apt-get does not install the latest monodevelop.
- insulanian 10y agoRelease notes [1] say: This is a preview of the upcoming Xamarin Studio 6.1 release. Is it already released? [1] https://developer.xamarin.com/releases/studio/xamarin.studio_6.1/xamarin.studio_6.1/ https://developer.xamarin.com/releases/studio/xamarin.studio...
- sremani 10y agoYes, its already out. I had couple of hiccups while installing but was able to install it from Github.