If you're building SharpDevelop from our Subversion repository, you might already have noticed it: The trunk of the repository now contains SharpDevelop 2.1 (Codename "Serralongue").

Changes in the 2.1 line so far: The Subversion AddIn was reactivated (note that it does not work on x64), a Boo interpreter pad was added, the docking library was updated and now supports VS2005-style "dock helpers", and you can now choose the target framework version for VB projects.

Our wiki gives more information on how to get the code from the repository; the build server will build the 2.0 line only for the moment.

If you are already using the repository but want to stay on the 2.0 line, you will have to switch your working copy using this command:
svn switch svn://sharpdevelop.net/sharpdevelop/branches/2.0/SharpDevelop

Bug fixes are committed to the 2.0 branch only and every week they will be merged back to 2.1. New features will be added to 2.1 only.

Please see the Beta 2 Announcement in our forum for details, a couple of interesting things have happened since Beta 1! Enjoy, and keep the suggestions and bug reports coming!

Thanks to a patch from John Simons (he contributed an implementation for the necessary JScript Gobals object), SharpDevelop2 can now persist the Html Help settings. An example for the settings are the language filters - the below screenshot shows the default way a topic is being displayed:

Information on syntax and usage is displayed for all languages, which in most cases is inappropriate. So you can adapt the filter to your programming language preferences:

You could do that before revision 1058 too, however, upon closing and reopening (even the help browser), the language filter settings would have been lost. Now, this no longer happens (screenshot is after a restart, you simply have to trust me on this one - or even better, try the daily builds):

A seemingly small improvement, but I am sure that many developers will appreciate the effort that went into it!

Yesterday, Matt checked in support for code coverage. As usual, he wrote a great tutorial on how to use it in his blog Code Coverage with NCover.

Starting with revision 1038, the post install tasks batch file compiles (ngens) the main assemblies to native code. The main intention is to speed up initial startup of the application. Affected assemblies: SharpDevelop.exe, ICSharpCode.Core, log4net, ICSharpCode.SharpDevelop, ICSharpCode.TextEditor, WeifenLuo.WinFormsUI.Docking and ICSharpCode.NRefactory. Please note that PostInstallTasks.bat is called only from setup, so if you are building from source, you have to start it yourself.

I've published a CodeProject article about ICSharpCode.Core. It demonstrates how you can use the SharpDevelop Core to create your own applications. Link: http://www.codeproject.com/csharp/ICSharpCodeCore.asp

This video shows what you need to make your AddIns ready for the AddIn Manager and package them as ".sdaddin"-files.

AddInManager.wmv (2,37 MB; 05:12 m)

It uses the Image Viewer addin from the third AddIn-writing tutorial.

Additional downloads:
MyTestAddIn.AddInManager.zip (4,53 KB) - source code of the test AddIn
ImageViewer.sdaddin.zip (2,92 KB) - binary package of the test addin (remove the ".zip" extension, it's just there because this blog doesn't accept ".sdaddin" files)

There is a bug SharpDevelop 2 Beta 1 which causes the AddInManager to crash when opening the .sdaddin-file created in this video. It has been fixed in build 940, so make sure you get a recent build from the build server.

We just put the finishing touches on Beta 1 of SharpDevelop2. The official build number is 2.0.0.922, and as such is a LGPL-licensed release (read more here). Download