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

Are Embedded Symbols better than Symbol Packages? #1

Closed
Turnerj opened this issue Feb 3, 2022 · 3 comments
Closed

Are Embedded Symbols better than Symbol Packages? #1

Turnerj opened this issue Feb 3, 2022 · 3 comments

Comments

@Turnerj
Copy link
Owner

Turnerj commented Feb 3, 2022

From Twitter: https://twitter.com/SimonCropp/status/1489212671694032897

i recommend embedded symbols over a symbols package. embedded symbols are smaller than pdbs and give you stack traces in production

  • Does embedded symbols make it easier for developers to use your package?
  • Test how stack traces look for embedded-vs-not - is the difference helpful?
  • MSDN says embedded symbols make NuGet packages larger - is that a problem?
@Turnerj
Copy link
Owner Author

Turnerj commented Feb 3, 2022

There is already a large conversation about switching the default to embedded symbols in the .NET SDK. Worth using the details there to weigh in on the best option here.

dotnet/sdk#2679

@Turnerj Turnerj changed the title Investigate whether Embedded Symbols are better than Symbol Packages Are Embedded Symbols better than Symbol Packages? Feb 3, 2022
@Turnerj
Copy link
Owner Author

Turnerj commented Feb 3, 2022

Additionally there is a Microsoft blog post talking about Source Link and refers to embedded symbols too: https://devblogs.microsoft.com/dotnet/producing-packages-with-source-link/

@Turnerj
Copy link
Owner Author

Turnerj commented Feb 4, 2022

Checklist has been updated to recommend embedded symbols

@Turnerj Turnerj closed this as completed Feb 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant