Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update symbol packages guidance #9110

Merged
merged 6 commits into from
Nov 20, 2018
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/standard/library-guidance/nuget.md
Original file line number Diff line number Diff line change
Expand Up @@ -110,7 +110,9 @@ An alternative to creating a symbol package is embedding symbol files in the mai

**✔️ CONSIDER** embedding symbol files in the main NuGet package.

**❌ AVOID** creating a symbols package containing symbol files.
> Embedding symbol files in the main NuGet package gives developers a better debugging experience by default. They don't need to find and configure the NuGet symbol server in their IDE to get symbol files.
>
> The downside to embedded symbol files is they increase the package size by about 30% for .NET libraries compiled using SDK-style projects. If package size is a concern then you should publish symbols in a symbol package instead.
JamesNK marked this conversation as resolved.
Show resolved Hide resolved

>[!div class="step-by-step"]
[Previous](./strong-naming.md)
Expand Down