Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

dotnet pack doesn't preserve directory structure for included files.

See original GitHub issue

Steps to reproduce

Run dotnet pack on the below project which has

"packOptions": {
    "files": {
      "mappings": {
        "Templates/": "Templates/"
      }
    }
  }

https://github.com/prafullbhosale/PackRepro

Expected behavior

The generated nupkg has the directory structure

/Templates
      |__ Folder1
                |__File.txt
      |__ Folder2
                |__File.txt

Actual behavior

/Templates
      |__File.txt
      |__File.txt

Environment data

dotnet --info output:

D:\Projects\pack>dotnet --info
.NET Command Line Tools (1.0.0-rc2-002543)

Product Information:
 Version:     1.0.0-rc2-002543
 Commit Sha:  38d0c28a1e

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.10586
 OS Platform: Windows
 RID:         win10-x64

Issue Analytics

State:
Created 7 years ago
Comments:9 (8 by maintainers)

Top GitHub Comments

1reaction

TheRealPiotrPcommented, May 3, 2016

Since we have ample workarounds, putting in rtm milestone.

0reactions

ajaybhargavbcommented, May 4, 2016

Spoke to @pranavkm. Symbol packages have been using the wrong folder structure before the schema changes and using compile include actually fixes the problem but also breaks the assumptions. So no change is currently needed for this other that to add a test to verify this scenario. I’ll file an issue in repos that need to be updated to use the new structure.