Make sure you check out the contributor blogs. Just recently, Matt blogged about Mono integration (here and here), targetting different framework versions, as well as NAnt integration in SharpDevelop 2.0.

Revision 549 adds support to use older versions of the C# compiler with SharpDevelop 2.0.

In the "Compiling" options page of the project, you can set the version you want to use. If you use anything else than "Default (.NET 2.0)", SharpDevelop will modify the project file to use a custom MsBuild target file from the SharpDevelop directory that allows you to specify a different compiler version and reference older versions of mscorlib and the System libraries.

If you want to use MsBuild.exe in the command line to compile your projects, you will now need to specify the directory where SharpDevelop is installed:

"MsBuild /property:SharpDevelopBinPath=C:\Programs\SharpDevelop\2.0\bin"

I have now added a backend binding for the language Boo to SharpDevelop 2.0.

Boo is a new object-oriented statically typed programming language for the .NET Framework with a Python-inspired syntax and a special focus on language and compiler extensibility.

The most important feature - compiling - is not yet supported because currently there is no MsBuild task for Boo. Code completion is already implemented using the parser of the Boo compiler with a custom resolver using SharpDevelop's type system. Because BooBinding is implementing SharpDevelop's parser and resolver interfaces, all the new features like tooltips, find references etc. work for Boo, too.

Code completion for Boo's type inference (a feature that C# 3.0 and VB 9 will get) is already implemented, at least for local variables. You can expect that code completion support will be extended during the next weeks and support for compiling Boo applications inside the IDE will be added.

A Boo forms designer might be coming, too.

When moving to the latest dasBlog version, we also set up a dedicated host for the team blog. This will make it easier for us to run the sites with different versions of ASP.NET.

Yesterday, we have released builds for the 1.1 series, as well as another standalone setup for the 2.0 alpha. The former can be downloaded from our download page, the latter is only available on our sf.net download page.

This video is a quick introduction to the new bookmarks, search & replace, go to, help system, classes pad and some refactoring inside SharpDevelop 2.0:

QuickTourOfCorsavy.wmv (4.67 MB)

Today, we switched from Snitz Forum to Community Server. The main reason for this switch was performance-related: the original forum has outgrown its backend database. We tried to postpone - or put off - that necessary step for long.

One reason was that I originally planned to migrate the data from Snitz to CS, but that turned out to be a rather nasty process (the schemas are way too different, not to speak of user profiles and password storage). So it was decided to leave the old forum up and running in read-only mode, and have all new posts in the new forum.

Matt Ward just recently added support for MSBuild files to the XML Editor inside #develop:

MSBuildCompletion.wmv (2.82 MB)

You can try this feature yourself by downloading the hot off the press #develop Corsavy alpha. Read the announcement I posted in our new forum.

The video about the integrated debugger in #develop 2.0 whetted your appetite? You want to take the current bits for a spin? So here you go, but be warned: the bits you are going to grab are neither stabilized nor heavily tested.

First, read up on repository access in our Wiki:

Using the repository

The checkout command needs to be modified as follows:

svn co svn://sharpdevelop.net/corsavy/trunk SharpDevelop

The bits in the repository currently compile against the .NET Framework 2.0 Beta 2, which can be downloaded freely here. At a minimum, you need the Runtime. SDK is recommended though.

A few more notes: please use the mailing lists for reporting problems etc. Which ones to use are described in the aforementioned Wiki article. These haven't changed from Fidalgo to Corsavy. Please be sure to not only include the error message, but also the steps to reproduce as well as files pertinent to make is reproducible.

Next week we plan to release an alpha binary for those of you who don't want or cannot access our Subversion repository.

This video is a short demonstration of the debugger that is integrated with Corsavy, the version 2.0 of #develop, targetting .NET 2.0. The debugger is being implemented by David Srbecky, and you can read about the debugger in the Wiki. However, you came here for the video, so here you go:

DebuggerInCorsavy.wmv (5.01 MB)

David did a great job to get this beast up and running, and you can expect more features to be added in the near future.