-
Notifications
You must be signed in to change notification settings - Fork 224
Allow additional files in the nupkg #848
Comments
BTW, this is a different way of asking for #45 |
Ping... our workaround depends on an external-to-DNX solution that leverages |
@davidfowl I don't think you're looking into this. Could you move to another milestone (or in 1.0.0 backlog?) |
I prefer putting the destination on the left, and I'd like to see if we can get globbing in there. We'll be talking about this in the design meeting today. |
W00t! We have workarounds in EntityFramework and in Microsoft.Data.Sqlite for this... |
Initial design notes. We're going to iterate on it tomorrow. /cc @davidfowl {
"packageFiles": {
"dest": "src"
}
} I think that the "source" file specifier needs to be able to be an array. Basically, if the thing on the right ends up evaluating to multiple file names, the thing on the left is a folder. Otherwise, the thing on the left is a file and must have the full name of the file. Because the body of this property is a JSON dictionary, we are restricted to only having one entry per destination. {
"packageFiles": {
"test": ["a.txt", "b.txt"],
"README.md": "docs/README.md"
}
} |
This is just about how to add files to the generated nupkg, but not about how they will be consumed, right? |
@MiguelAlho That's correct. |
Additional design notes:
|
Similar to a nuspec file, project.json should allow you to specify additional files to include in the nupkg. I imagine a format like the following.
We currently do this post-build on the following packages.
The text was updated successfully, but these errors were encountered: