Thanks to Randy there’s a FAQ section in this blog right now. So if there are questions rising up, leave a feedback and I’ll try to answer them + enter the answer to this section.

I’ve used the Arconix FAQ plugin for WordPress to realize the page.

There’s some good news concerning the addin which brings better and D-specific debugging to MonoDevelop — Invoking an object’s toString() method has become possible again..I’ve also made couple of things easier, so there’s no manual reassembling and other hard circumstances required to inject the toString-examiner on different platforms anymore!

Have some screenshots:

Despite the lucky message of having some project activity again there are still way to many unstable and weak points which make real debugging with this addin quite difficult. So lean back, and await the new stuff! (..or come on contributing)

I’ve just pulled, built, packaged and uploaded the latest monodevelop master version (which apparently is 4.0.6) to http://simendsjo.me/files/abothe – Thanks to simendsjo for letting me host the files there!

Mono-D works with this version, of course.

Cheers,
Alex

[UPDATE May 12] Updated to Mono 3.0.11

Download MonoDevelop master and Mono here!

Extract the mono directory into /opt/ and you’ll be able to start MonoDevelop via /opt/mono/bin/monodevelop!
(sudo tar -xPf MonoDevelop.x64.Master.tar.xz should do it)

I’ve tested it under Manjaro x64, x86 (an Arch derivative) and Mint 13 x86, so it should work under other distros either.

There shouldn’t be any further requirements than this archive. All the stuff except gtk-sharp2 has been built from master, so this build should be an absolutely fresh one!

EDIT: I’ve uploaded a new archive that has a library filename resolution issue fixed. For individual configurations, check the /opt/mono/bin/monodevelop startup script.

While trying to improve some things regarding parsing import statements, I’ve invented some null ref exceptions – which I fixed in this release.

Furthermore: This project is not dead yet! It just has become difficult for me to find some time for coding due to more intense tasks I’ve got to do for my studying..4th semester ain’t easy anymore :-/

Though I released it a couple of days ago I’ll do a release note now:

I’ve added a ‘native’ support for Dub projects. You just have to open the package.json meta file that is located inside a D project’s folder in order to have it opened in Xamarin Studio / MonoDevelop – no need for creating an artificial .dproj/.sln file via dub anymore!

The support is currently very limited though – but you can build and execute projects with it. All build configuration has to be done in the package.json now; Currently there aren’t any control panels – and trying to edit a project’s settings will throw exceptions – but you also don’t have to configure it in MD anymore..

If the package.json got edited while the project is opened, it’ll reload the file automatically! No need to reopen it all the time!

During the Mono/XamarinStudio release ‘crisis’ on x86 Linuxes, I was noticed that the build routine on XamarinStudio’s internal addin releasing system works again for Mono-D for Linux and Mac platforms (only!) – which is a slight progress (again). Due to this you don’t have to enter the mono-d.alexanderbothe.com repo path manually into the addin manager but you can still access the latest build directly in the Beta-Addins channel.

Noticed the new release by coincidence yesterday – and updated the mono-d code immediately. Unfortunately, I can’t build XS under Mint anymore due to a mono version increase + my mono installation got messed up due to experimenting with Mono 3.0.6

Could anyone load the latest XS/MonoDevelop binaries up to a public place so we can access it?

In the mean time, you can revert your Mono-D version right here!

To prevent double issue reports due to incompatibilities w/ the new 0.5.2 version of Mono-D:

https://github.com/aBothe/Mono-D/issues/251

[UPDATE May 2013] I’ve packed and uploaded the latest version to http://simendsjo.me/files/abothe/

[Update] Fuck it, several parts of the completion & context recognition are still broken. More updates are coming soon.

I’ve fixed another bunch of bugs/implemented stuff during the last few days:

• Regression: Method locals weren’t shown in the completion.
• Regression: Completion didn’t trigger on method parameters etc.
• Work-around/Good compromise for too long template deduction times. #243
• Prefix all ‘extra linker arguments’ with -L when building projects in one step.
• Show default compiler in the global compiler options by default #221
• Intellisense didn’t process Up & Down keystrokes / immediately closed down the completion window #245
• Established detection in the completion whether an expression is parsed
• Fixed completion within enum definition blocks
• null-ref exception when typing a space after e.g. myTemplate!()  #244
• writeln(asdf,) could’t be parsed though it’s marked as legal in the specs #248
• Only show classes, interfaces and templates when completing base classes. #236
• Template parameter insights were not displayed.
• Added AST modifier which finally solves the completion issues e.g. when entering a line break at a method’s body ending and the method’s locals won’t show up anymore.
• Fixed references finding for implicit template properties. #234
• When formatting text parts, indentation replacements are now combined to one undo group. #242
• Show param insight for delegates #241