LicensingKit 2.0.1

LicensingKit

LicensingKit is a library to make licensing C# projects easier.

This library is meant to help developers communicate the License of their C# project to the developer users of the project. This library does not enforce any choice of license and you are equally free to use it in a proprietary project or an open source project.

Developers of strictly open source projects may not find as much benefit with this library as those of proprietary or dual/triple licensed projects. Nonetheless the same features are available to all users.

Use Cases for this library

If you have a C# project where your end users are other developers and any of the following applies to you, you may wish to consider using this project:

• The users of your project are likely to not understand all the requirements of the license of your project and how it affects their project.
• The users of your project may try to intentionally infringe upon your license without you realising.
• The users of your project could inadvertently infringe upon your license without meaning to.
• Your project is licensed under multiple licenses and it may be hard for the user to see or manage under what license they are using your project.

How do I use LicensingKit in my project?

1. Download LicensingKit from [Nuget]
2. Setup a class to store your license objects
3. Make a Settings class to store the user's selected license
4. Modify the Constants class to make LicensingKit calls
5. Adding license check calls to your code

License

This library is licensed under the LGPLv3 or any later version.

If you modify the source code of this library and publish that source code then you are also required to publish the source code of your modified version of the library.

Distributing an unmodified version of this library (such as from Nuget or from the releases page) in your project does not require you to publish the source code of this library or your project regardless of whether you statically or dynamically link this library to your project.

Isn't the LGPL antithetical to Proprietary Software? Why are you enabling Proprietary Software Users?

1. No, as far as we are aware the LGPL isn't antithetical to Proprietary Software and exists because the gap must be bridged between open source and proprietary software. The LGPL is a way to help bridge that gap.

2. We do not enable Proprietary Software anymore than Proprietary Software is already enabled or encouraged. We are merely providing a tool that can help both open source developers and proprietary developers or developers that use both like us.