You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When adding an open source library to an application, we are usually required to include the library's license along with the DLL when distributing the application.
Currently there is no standard way of handling this, which means there is an often overlooked manual step necessary for any project which distributes the application.
The text was updated successfully, but these errors were encountered:
In the package definition, the library publisher can include a "License File" tag.
When an application takes a dependency on a library, the license file is copied to the project's "\licenses" folder with "None/Copy if Newer" set as the build action.
The filename will be prefixed with the package name and version.
When adding an open source library to an application, we are usually required to include the library's license along with the DLL when distributing the application.
Currently there is no standard way of handling this, which means there is an often overlooked manual step necessary for any project which distributes the application.
The text was updated successfully, but these errors were encountered: