You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a NuGet package includes PDBs in its lib folder, the legacy project system copies the PDB as well as the assembly into the build output folder.
The new project system only copies the assembly.
We've recently added source link support , and when using the new project system with a .NET Core target, everything works fine since the PDB is referenced correctly from the global NuGet package folder.
However, because the PDB isn't copied for a .NET Framework target, we don't get any of the benefit of our sourcelinked PDB.
It would be great if the new project system would behave like the legacy project system in this case, and also copy the PDB into the project's build output folder.
The text was updated successfully, but these errors were encountered:
When a NuGet package includes PDBs in its lib folder, the legacy project system copies the PDB as well as the assembly into the build output folder.
The new project system only copies the assembly.
We've recently added source link support , and when using the new project system with a .NET Core target, everything works fine since the PDB is referenced correctly from the global NuGet package folder.
However, because the PDB isn't copied for a .NET Framework target, we don't get any of the benefit of our sourcelinked PDB.
It would be great if the new project system would behave like the legacy project system in this case, and also copy the PDB into the project's build output folder.
The text was updated successfully, but these errors were encountered: