Many people requested a setup version for SharpDevelop 2 on .NET 2.0.50727.42. Normally Chris is doing the releases, but there were so many requests that I had to do it now.

I don't have access to the source forge page, so the file is hosted here on the team blog. To reduce the file size a bit, the incomplete SubversionAddin is not included in this setup.

Note: there are now newer setup versions available on the build server.
Old Download: Corsavy 654 Setup.exe (2,86 MB)

Changes to revision 593 (the last setup version) are: Many bugfixes, including critical bugs with the new MSBuild version; big improvements to BooBinding and a new feature called "Typing-Time Type Inference": Type "? name = ...;" or "Dim name As ? = ..." and SharpDevelop will substitute the question mark with the type of "...".

The final version of .NET 2.0 has been released and SharpDevelop in the repository has been fixed to run on it. A setup will be made available for download in some days, until then you have to use the repository if you are interested in .NET 2.0.

.NET 2.0 download: The Framework[^] and the SDK[^]

All of the problems were due to changes in MSBuild. One old hack could be removed because MSBuild bug was fixed, but two new hacks had to be introduced for two new bugs. (not counting the strange "BuildProject" properties behaviour)

The new MSBuild does not understand the our solution (.sln) files because they were missing the SolutionConfiguration section. SharpDevelop will automatically add that section if you open a solution, so you won't notice the problem.

The third video explains how to create a primary display binding that can view images:

Tutorial3.wmv (3,78 MB, 07:38m)

Again, this tutorial starts with opening the AddIn created in tutorial 1, so make sure you watch that first.

MyTestAddIn.3.zip (4,06 KB) contains the addin as it should be after following the steps in this tutorial. It uses "..\Corsavy" as relative path to the SharpDevelop checkout directory, so make sure you extract it to the correct location.

This video explains how you can write a SharpDevelop addin that provides a tab page "Preview" that displays .html files.

Tutorial2.wmv (3.25 MB, 07:25 m)

The video starts with opening the AddIn created in tutorial 1, so make sure you watch that first.

I hope these tutorials will help some developers getting started with AddIn development so SharpDevelop 2 will have a number of AddIns available.

This video explains how to create an AddIn for SharpDevelop 2.0:

Tutorial1.wmv (5.2 MB, 05:19 m)

It is the first part of a series that will demonstrate some example AddIns and how to create them. The next parts will be based on the AddIn we set up in here, so make sure you follow the steps!

A page in the wiki contains the full list of the tutorials published so far.

EDIT: Note that the repository URL has changed since the video has been recorded. The new address is svn://sharpdevelop.net/sharpdevelop/trunk

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.