I love the ability to push packages and symbol packages to nuget and symbolsource.org with a simple command.
However, creating symbols packages is overly complicated right now. The project file approach (.csproj) is a neat trick, but not practical except in the most basic situation (no support for multiple projects, multiple target frameworks, external builds,
etc). There needs to be a streamlined approach for building .symbols.nupkg companion packages from a given nuspec file. I do not want to use the conventional folders approach to specifying my files, as it seems tedious to have to move files around
the filesystem, instead of referencing them where they are in my source tree.
Currently, this requires the following process:
create a single nuspec file, it uses file elements to specify all of the files that will be included in the library and symbol packages.
call nuget pack myspec.nuspec rename the created myspec.1.0.0.nupkg to myspec.1.0.0.symbols.nupkg call nuget pack myspec.nuspec -Exclude ***.pdb -Exclude ***.cs
I now have myspec.1.0.0.nupkg and myspec.1.0.0.symbols.nupkg.
This seems like a common scenario that should be baked in somehow. Currently, the -Symbols option for the pack command is only valid when building from a package. How about we allow use of the -Symbols option with .nuspec files, and give it the following
build the source package, and give it the .symbols.nupkgs name build the lib package, automatically excluding all pdbs, and the entire /src target folder
If doing 2 builds would be too complicated in a single command, maybe -Symbols option just does step 1, and a -NoSource option does step 2.
Are there any other ideas out there on how to support symbol package creation from a nuspec file?