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

Microsoft.Data.SqlClient.SNI.pdb gets generated after the update to Microsoft.Data.SqlClient 2.0.0 #674

Closed
emirkljucanin opened this issue Jul 30, 2020 · 2 comments
Labels
Area\Native SNI Issues that are targeted to the Native SNI codebase.

Comments

@emirkljucanin
Copy link

emirkljucanin commented Jul 30, 2020

Our CI pipeline removes all .pdb-s from the publish folder before packaging. After updating Microsoft.Data.SqlClient 2.0.0 our ASP.net core app stopped working and we figure out that Microsoft.Data.SqlClient.SNI.pdb is required in Release\netcoreapp3.1\runtimes\win-x64\native in .deps.json.
Is this .pdb really necessary, or is there a workaround for not requiring it?

@karinazhou karinazhou added the Area\Native SNI Issues that are targeted to the Native SNI codebase. label Jul 30, 2020
@cheenamalhotra
Copy link
Member

Hi @kljuco

Based on discussions here: #644 (comment), we're planning to remove symbols in .NET Core native (SNI) NuGet. It's not required by driver, they're linked in deps.json from where without them publish doesn't happen. It's different how dotnet sdk handles PDBs for native-runtime v/s .net runtime packages.

@emirkljucanin
Copy link
Author

Great. Thank you :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area\Native SNI Issues that are targeted to the Native SNI codebase.
Projects
None yet
Development

No branches or pull requests

3 participants