-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Closed
Milestone
Description
Sample code:
- PackagedLibrary - library, which is packaged as NuGet, includes PDB file along with DLL; currently published as PackagedLibrary-1.0.0-beta.
- LibraryConsumer - ASP.NET Core 1.1 project, consumes library from NuGet.
Repro:
- Unzip, restore packages, rebuild all.
- Open LibraryConsumer\bin\Debug\net452\win7-x86. Observe that there's only PackagedLibrary.dll, but not PackagedLibrary.pdb
Expectation: PDB is also copied to consumer project output.
In fact, if you create a new ASP.NET Web Application (.NET Framework) project and add same package there (Install-Package -Id PackagedLibrary -Version 1.0.0-beta), you'll see PDB being copied to output.
Why is this important? The project I'm working on is a complex web application with a lot of dependencies on internal libraries. All libraries are indexing their source code in PDB and packaging PDBs along with DLLs. If problem occurs and library user needs to debug, they can simply step into the library call. If PDBs are not automatically copied, it's impossible to do (unless you know about this issue and copy PDBs manually).
macgyver76, ozziepeeps, jmelosegui and rshramko
Metadata
Metadata
Assignees
Labels
No labels