Thinking about plans for ROOT nuget packages. The scenarios it has to all work for are:
Build a C++ program that allows you to read and write ROOT files (like histograms).
Used in a C++ .NET program
Referenced by a library built with the above, that has been packaged into a nuget library.
Some other feature requirements:
Individual packages are small enough they can be uploaded to nuget.
If the build is done right, a symbol's package is uploaded to the proper debug symbol server (wow, that would be nice!).
Client C++ and .NET programs must "just work" in debug and release mode. Limitations to code should be clearly documented.
It could be that the last can't really be done easily, and should just be done by including the dll's directly in the packages.
