2

I am developing a .net core self-contained application for an embedded linux device. The software is part of the device image and won't be sold standalone nor it is downloadable in binary or source code form. As far as I know, .net core is licensed under MIT, but with all its dependencies to native libraries and nuget packages there are a lot of questions. However, not all of them are specific for .netcore:

  • Nuget packages usually include a LICENSE file. Does this license cover everything coming with that package (including other nuget references and third-party libraries)?

  • Nuget packages often contain a THIRD-PARTY-NOTICE file. Is this just for information or is this just another "license" file which must be considered?

  • As I only deliver binaries (everything produced via dotnet publish), is it enough if I have the license information for each file in the publish folder or do I have to include licenses of packages which don't result in a file in the publish folder? (Currently I have about 200 packages detected, but only 20 of them have a direct link to a file in the published folder).

Can anyone recommend a good website/book about the topic. It seems there are a lot of tools and information for programming languages like C where (typically) no package managers are involved and licenses are available in the sources.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.