What license to use for a new OSS project in .NET.
Hi Anyone who is of great importance in TDD and who is using .NET will end up with the issue of closed classes. Some classes in the .NET library are sealed, which prevents them from being extended (and thus mocks them). To add insult to injury, Microsoft does not provide interfaces for these classes. The workings of all classes tend to be the ones that bind you to things like IO (FileInfo, DirectoryInfo) or IIS (HttpContext, HttpRequest, HttpResponse).
Eventually you just end up writing your own interfaces and corresponding wrapper classes. I've done this so many times that I decided to just make an open source project out of it for everyone to use.
My question is which license to use / use. I disagree with the Apache / BSD style license; but can i use this with .NET? Can I use the GPL and let people use it in commercial applications? Or should I be using something like Microsoft Permissive License?
source to share
You can use any license you want to use with .NET - the framework and platform does not block you on any particular license.
As for your specific questions:
I am partial to the Apache / BSD style license; but can i use this with .NET?
Yes, it is perfectly acceptable for use in .NET applications and is a good option as well as an MIT license.
Can I use the GPL and let people use it in commercial applications?
The GPL places some pretty tight restrictions on usage, which limits commercial takeover (since it forces users to redistribute their application based on your library as the GPL). The LGPL is an option that does not prohibit commercial use for almost as much.
Or should I be using something like Microsoft Permissive License?
This is much more common with .NET libraries, and will be much more familiar to many .NET developers. If you are happy with the terms of this license, this is a very good option (at least from the point of view of not limiting use only under the license).
source to share
If you want to be completely open, use the MIT license.
Copyright (c)
year
copyright holders
Permission is hereby granted, free from instructing any person who has received a copy of this software and associated documentation files ("Software"), to engage in the Software without limitation, including without limitation of the rights to use, copy, modify, combine, publish , distribute, sublicense and / or sell copies of the Software and authorize persons to whom the Software is provided, therefore, subject to the following Terms:
The above copyright notice and permission notice must be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT PARTNERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN ACTION AS A CONTRACT ACTION OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER RELEVANT IN THE SOFTWARE.
source to share