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.