-
Hello, thanks for the tool, it make dealing with references a breeze, but i'm trying to figuring out how to create a separate .snupkg for debug symbol and i'm somewhat stumped. As stated here it's enough to add There is some way to replicate the function of dotnet pack and create a snupkg alongside the nupkg? If may add another question: the solution that want to packetize contains some old csproj projects (i'm targeting net48) and apparently there is no way to exclude those pdb from the output, oldcsproj seems lacking the |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi there! I don't believe in separate symbol packages ;-). The portable pdb format is extremely compact, and can even be embedded in the dlls. Separate symbol packages add little to no value IMHO. Hence, they are not supported in nugetizer. I haven't tested things with old csproj at all, but I heard the new conversion tool to SDK-style should make that a breeze. Perhaps you can update the project file, while keeping net48 as the target? |
Beta Was this translation helpful? Give feedback.
Hi there! I don't believe in separate symbol packages ;-). The portable pdb format is extremely compact, and can even be embedded in the dlls. Separate symbol packages add little to no value IMHO. Hence, they are not supported in nugetizer.
I haven't tested things with old csproj at all, but I heard the new conversion tool to SDK-style should make that a breeze. Perhaps you can update the project file, while keeping net48 as the target?