More information here. The release was originally scheduled for a week earlier, however, bug fixing took us a little longer so we decided to slip.

Our build automation system has changed: up until yesterday, we were using CruiseControl.NET to kick off an NAnt script to run our daily build. Now we are using MSBuild end-to-end in our build system, with a much cleaner architecture than before:

1. CruiseControl.NET kicks off the build by checking out the latest changes. The build is triggered either based on time (for the daily builds) or on check in (continuous integration).
2. After check out, CruiseControl.NET hands over to KickStart.proj, which we wrote and placed in the root of our CC.NET installation. This MSBuild script sets a couple of properties, and then delegates further work to
3. Automated.proj. This MSBuild script is part of the checked out project that is to be built. It does all the heavy lifting, like build, unit tests or setup creation.

The obvious advantage of this setup: the build server doesn't know a thing about what the project needs (tools, libraries, you name it) to be built properly. Thus we are now doing our daily SharpDevelop builds, our CI SharpDevelop builds as well as SharpReport daily builds using one standardised setup. It took us a while to get into gear (old habits die hard, and why change a running system), but it is now fully operational.

Bootnote You can find all of our scripts in the repository. However, you need to check out trunk/SharpDevelopBuildServer instead of trunk/SharpDevelop.

Yesterday, we set up an anonymous Subversion mirror for the SharpDevelop repository. Instructions on how to use it can be found here:

http://wiki.sharpdevelop.net/default.aspx/SharpDevelop.UsingTheRepository

It replicates from the development repository every six hours starting at 3:15AM CET. Please note that we might remove anonymous access to the development repository in the future, so please switch over to the new mirror.

The code converter has a new home: http://codeconverter.sharpdevelop.net/ - please update your bookmarks, as well as applications that are using our conversion service. In addition to the move, we upgraded from revision 1591 to 2063.

Daniel mentioned in his blog post Open Source Code Statistics that earlier work on SharpDevelop 2.0 (code name Corsavy) was done in a non-public repository and thus not included in the statistics. The reason is that this initial Corsavy repository gave way to the current SharpDevelop repository, where all the work was imported in one fell swoop. Therefore no public knowledge exists on what happened in the early days of developing version 2.0. Well, this post intends to correct this situation.

First and foremost: the actual repository does not exist any more. All that remains are the commit messages collected in an mbox file:

CorsavyCommit.zip (154.11 KB)

To view this mbox file, please use the Windows MBox Viewer. All you need to do is File / Open and browse to the folder where you extracted CorsavyCommit.mbx to. Then you can browse the history of the internal repository for Corsavy:

A couple of things to note on the history:

• The repository was operational from 12/31/2004 till 8/16/2005, when it was transitioned to the current repository.
• It contains roughly 400 commits
• Yes, the revision numbers do start at 1 again in the middle of the commit messages. Reason is that our initial Subversion server at this time had issues. So we had to start over with a new repository.

I hope that you will find this excursion on history lane interesting, especially on how long we actually worked on version 2.0 before going public. 

ohloh.net is a service that analyses the source code of open source projects and creates statistics.

Click on this button to see the statictics for the SharpDevelop repository: 

All information on that page was automatically created by the service by looking at the subversion repository. It is wrong on the following points:

• project age. Only the public repository of SharpDevelop 2.0 has been analysed. Earlier work on SharpDevelop 2.0, and the whole work on SharpDevelop 1.x and earlier beta versions is not included in the statistics. Old code taken over to the new repository was attributed to Mike Krüger.
• License. It has found license headers in the source code of log4net and other libraries/tools included in the repository. That code is attributed to the person who added the library to SharpDevelop. The real license for SharpDevelop code (LGPL) is not found at all because we don't use the standard LGPL header.
• The line count is slightly wrong for the same reason as above.
• Only contributors having commit access are mentioned, patches are attributed to the person who checked in the patch.

On the contributors page, you can see activity graphs for the individual developers. And you can see the comment ratio, which unfortunately is quite low (far below C# average according to the "Factoids"), but other popular open source projects like Firefox, OpenOffice or MediaWiki seem to have the same problem.

A rather informal launch as I am here in Barcelona at TechEd Developers - John (SharpZipLib maintainer) has released v0.85 for both .NET 1.1 and .NET 2.0:

• Compiled for .NET 1.1
• Compiled for .NET 2.0
• The Samples & The Source

The SharpZipLib download page doesn't yet reflect the new version, so this is the place to get the version first!

Because we shipped a non-working version of SharpReport with build 2.1.0.2006, we have released build 2.1.0.2017 (Beta 2b) for those of you that test SharpReport inside SharpDevelop. The upshot: you now have the latest and greatest bits of SharpReport in SharpDevelop2 2.1 Beta 2. Download