Reading over the manifest file article at http://www.dnnsoftware.com/docs/developers/extensions/dnn-manifest-schema.html I ran into a collapse of terms between 'Component' in the context of a Manifest, 'Library' in the context of a Manifest and 'Component' in the context of a VS DNN Project.
It seemed at first that VS Project Components were listed in the <Components> tag with an individual entry for each. These contain Class Libraries. These compile into the assembly and are referenced by the code behind, of course.
For comparison I looked up these terms:
.NET Framework (current version) The .NET Framework class library is a library of classes, interfaces, and value types that provide access to system functionality. It is the foundation on which .NET Framework applications, components, and controls are built. (https://msdn.microsoft.com/en-us/library/gg145045(v=vs.110).aspx)
In R, a package is a collection of R functions, data and compiled code. The location where the packages are stored is called the library. If there is a particular functionality that you require, you can download the package from the appropriate site and it will be stored in your library.Nov 13, 2014 (https://stackoverflow.com/questions/26900228/what-is-the-difference-between-a-library-and-a-package-in-r)
So I opened up a DNN Manifest for the Reports module and sorted a lot of the collapse of terms out.
However, just what is a DNN Library package type? I can look over the list of the other types and pretty much do know what they are even if I have not ever created one:
type can be one of the following:
- Auth_System
- Container
- CoreLanguagePack
- DashboardControl
- ExtensionLanguagePack
- JavaScript_Library
- Library I can't seem to locate a real-world example of a DNN Library Package
- Module
- Provider
- Skin
- SkinObject
- other custom extension types