aBothe
xamarin 6.0 not supported
today i got an xamarin update (6.0 build 4520) and mono-d is nowhere to be found suddenly
Did they really release 6.0? For now, I'd recommed to downgrade XS, as I have to release MD for 6.0 dediactedly.
is there a way to downgrade XS from the IDE ? The website xamarin.com seems to only allow downloads if you register for that piece of crap...
I don't upgrade without backing up previous versions, I've been screwed too many times. Here it is
http://globecsys.com/XamarinStudio-5.10.0.871-0.msi
@etcimon you are great!! you do not happen to have the osx version too ? :P
soo.. I may continue de-bugging mono-d without getting cold sweat about inconsistent version bumps?
I won't upgrade to 6.0 until mono-d is 4-5 versions into stable support for it :)
well fortunately, it's not about broken APIs but just about silly dependency constraints this time. (As I had a local build for MD 6.0 back some..months ago :fried_shrimp:) https://github.com/aBothe/Mono-D/tree/md60
@etcimon really freaking awesome, thanks the dmg was exactly what i was looking for!
As long as Xamarin won't release its 6.X version as stable, there's no new API-bumped Mono-D version coming out. Quite ridiculous, or should I dismiss that stubborn policy and screw some users? :P
I though Mono-D had only ever been tested on the latest alphas, or did that change recently?
I guess the history just repeats itself like when I switched from MonoDevelop 4.x to 5.x ..still the same ugly mess, also with distributions in Linux-repos - they all will likely just provide the 5.10 release, and until 6.0 is finally getting released, the maintainers will have stopped actually maintaining them. Interesting cycle, imho
In theory, yes. It's been like a year-long (at very least) "Beta" phase now whereas XS mostly runs bugfree (regarding the majority of features Mono-D uses, not sure about the Android bindings). Back then, I tended to recommend users to ignore the 'stable' version and head on the bleeding edge (which wasn't that bloody after all) Now there isn't even a monodevelop package in the AUR anymore, not bad. https://aur.archlinux.org/packages/?O=0&K=monodevelop
Okay, got some news. After having finally rebuilt MD 6.1 from the git master and having updated all referenced dlls, this is what comes up. That's a little effort needed to get it at least starting again :/
I'm on it, although it's very slow progress. Can't find time to take huge steps at once anymore.
Is there any news? I'm currently without any kind of IDE thanks to the recent update and the fact that a lot of dlangide has no official compiled versions.
Linux users can find version 5.10 here: http://download.mono-project.com/repo/debian/pool/main/m/monodevelop/monodevelop_5.10.0.871-0xamarin2_all.deb
Okay, got some news. After having finally rebuilt MD 6.1 from the git master and having updated all referenced dlls, this is what comes up. That's a little effort needed to get it at least starting again :/
Why not just block it at MD 5.10 for a while. Just fork a custom version of it and remove the auto update, focus on making the mono-d plugin "just work" with a custom package for each OS. No need to try catching a falling knife, it works great on 5.10 and that's all I really care about.
The reason why not to is because it would mean we aren't supporting the latest (and easiest to install) version of MonoDevelop.
Also, Microsoft has bought out Xamarin. I'm guessing this means that there will be many changes in the short term. But given the importance that Microsoft places on backward compatibility, I'm hoping things will stabilize at some point. This is just a guess though. I'm not sure how much actual involvement MS has in the project.
Would it be difficult to port this to intellij for instance? Things seem more stable over there
Yeah I was thinking it could be wrapped but I assume by your answer that it can't.. =)
Well, Visual D already uses Mono-D remotely to provide its auto-completion so it wouldn't be terrible, but the lexer and all the interaction with the IDE itself would still need to be written for IntelliJ.
Hey there, I'm pretty sure that I won't accomplish many things over here anymore. Rewriting Mono-D or at least reusing parts of the D_Parser for some Visual Studio Code extension or some other smallish IDE might make things easier for sure, though.
Hey there, I'm pretty sure that I won't accomplish many things over here anymore.
Is that a resignation? :-o
Considering my lack of motivation to put hands on things on a regular basis after work, sort of, yes. Despite that, @NightmareX1337 approached me on whether he might continue development, or at least do some active support. I'll be there to answer questions, merge things and provide little code support.
Okay, just want to say thanks for the good work you put in, this is some very professional tooling and the user experience is top notch.