I'm looking to repurpose the nuget package management system to package plug-ins for an application. These plug-in are still .NET assemblies, but the point is they would be installed directly into an application instead of being added to and referenced by a visual studio (code) project.
Typically when packaging .nupkg files special directories are create like /lib/net47,/tools or /content. Is this structure fundamentally required by nuget, or is this only required for visual studio (code)?
If i create a .nupkg file with a .nuspec file but a totally custom structure of other files will the package still be compatible with nuget.org or other repositories?
In other words, do .nupkg files have any other requirements then containing a .nuspec file?
As far as I can tell nuget install simply downloads and extracts the contents of the .nupkg files.