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

The SharpDevelop project started out as a "better than Notepad" solution five years ago. At that time, releasing it under the GPL was a natural decision, as the tool side of open source was always released under the GPL. However, SharpDevelop no longer is a simple tool, it is a framework for developers to extend the premier Open Source IDE, as well as build their applications on top of it.

To extend our reach beyond what a GPL-licensed framework could achieve, we decided to change the license for SharpDevelop2 – beginning with build 2.0.0.919, SharpDevelop2 is now available under the LGPL.

This change of license from GPL to LGPL will allow users and developers to extend Sharpdevelop in ways that were up to now unthinkable. Creation of closed source AddIns now is possible without licensing hassles. Integrate the popular SharpDevelop text editor control in your application for free in its latest incarnation. Base your own AddIn based application on the proven and tested SharpDevelop Core architecture.

Voices from the team

"Our application framework has proven to be very successful for a large Windows application – #develop being testament to its flexibility and power." Christoph Wille, SharpDevelop Project Manager

"SharpDevelop's AddIn architecture convinced me of the worth of Open Source on .NET. With the newly added Addin Manager, managing this powerful architecture is now easier than ever before." Daniel Grunwald, SharpDevelop, Development Lead v2.0

"The SharpDevelop architecture made it so easy for me to create my reporting tool that I just went ahead and did it on my own before joining the SharpDevelop team." Peter Forstmeier, SharpDevelop, SharpReport Developer

"Judging from my inbox, Antarctica is the only continent where there is no known user of SharpDevelop." Bernhard Spuida, SharpDevelop, Localization and Support Manager

Frequently Asked Questions (FAQ)

Which versions of the software are affected by the license change?

The change from GPL to LGPL applies to source code of #develop version 2.0, starting with revision 919. Any code older than this revision will remain GPL-licensed. This means, the entire #develop 1.x series will remain GPL, and all the GPL restrictions remain in place for those versions.

Aren’t tools supposed to be licensed under GPL? Doesn’t SharpDevelop qualify as a tool?

Yes, you are right. However, SharpDevelop is a framework that is meant to be extensible. Just because we are shipping a lot of functionality out of the box doesn’t mean that others can’t or shouldn’t write addins for SharpDevelop. We want to foster an ecosystem of third-party addins, no matter under which open source license or even commercial.

What’s in for me (the developer) now that you changed the license?

We imagine two main scenarios: you writing arbitrarily-licensed addins for #develop, as well as you using our assemblies to build your applications (especially the core, the text editor and #report). After all, linking to our binary assemblies is now restriction-free. All we ask (but not require) is that you do not rename the assemblies you use (we see this as free PR for us).

What if I need to modify the assemblies to suit my needs?

The only difference between GPL and LGPL is the linking exception. So if you need to modify the source code, the restriction of shipping your source code modifications alongside the compiled binary still kicks in. If you do not want to ship your source code modification, get in touch with us.

Would you consider integrating my code changes so I don’t have to ship it?

Absolutely. If your changes are applicable to a more general audience (ie if it isn’t too specific or limited to a single scenario), please see our information on contributing http://wiki.sharpdevelop.net/default.aspx/SharpDevelop.HowCanIHelp. The advantage for you – if integrated, you no longer need to perform a custom build to keep your modifications in sync with our latest bug fixes. Aside from that, others might just have been waiting for the feature you implemented.

Can I take soure file xyz.cs and use it in my application?

The main difference between GPL and LGPL is the linking exception. If you want to incorporate some of our source files into your projects, you are still bound to license your code under a compatible license.

Where can I read about the LGPL?

At the authoritative source: http://www.fsf.org/licensing/licenses/lgpl.html

Did you read “Why you shouldn't use the Library GPL for your next library”?

Yes, we read RMS’ article at http://www.fsf.org/licensing/licenses/why-not-lgpl.html. Actually, we intentionally chose LGPL because “using the Library GPL permits use of the library in proprietary programs”.

OK – so why didn’t you go the whole nine yards and BSD-licensed the SharpDevelop code base?

Frankly, we do not want to see our code end up filleted to suit in various commercial applications.

I know SharpDevelop has been around for four years+, how were you able to change the license?

We require copyright assignments from all contributors. That is why it was rather easy for us, compared to other Open Source projects that didn’t have this policy in place and consequently ran into trouble when they needed to change their license.

CCNet 1.0 Final was released today, our build server has already been upgraded.

The code converter now goes the whole nine yards: C# to VB.NET, VB.NET to C#, C# to Boo and VB.NET to Boo. Additionally, it sports background information, and the converter has been revamped.

Also, there is a sample of how to employ the Web service in my other blog here. (download of executable and source code included)

Daniel's comment got me into gear, and not only did I implement the #develop way of code conversion, I also put it online so you can convert your source code easily:

Convert C# 2.0 Code to VB.NET 8.0

Daniel did a great video on what is possible with NRefactory. When I saw it, I felt that I had to build something with it - and so I set out to create a simple ASP.NET 2.0 page that converts C# source code to VB.NET source code (written in VB.NET, just to get my fingers dirty once in a while):

The code is pretty much the same as Daniel wrote, this time VB.NET:

Imports ICSharpCode.NRefactory.Parser
Imports ICSharpCode.NRefactory.Parser.AST
Imports ICSharpCode.NRefactory.PrettyPrinter

Imports System.IO

Partial Class CodeConvert Inherits System.Web.UI.Page

Protected Sub convertCode_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles convertCode.Click
   Dim input As New StringReader(inputTextBox.Text)
   Dim parser As IParser

   parser = ParserFactory.CreateParser(SupportedLanguage.CSharp, input)
   parser.Parse()

   If (parser.Errors.count > 0) Then
      outputTextBox.Text = parser.Errors.ErrorOutput
      Exit Sub
   End If

   Dim cu As CompilationUnit, output As IOutputASTVisitor
   cu = parser.CompilationUnit

   output = CType(New VBNetOutputVisitor(), IOutputASTVisitor)
   cu.AcceptVisitor(output, DBNull.Value)
   outputTextBox.Text = output.Text
End Sub
End Class

The source code for the entire Web application is provided in the download at the end of this blog entry. Feel free to add more features to it, just note that the code is GPL-licensed, so please make your changes public.

CodeConvert.NET.zip (114.98 KB)