"content" folders are not published if they don't contain at least one file
See original GitHub issueIf I specify a content
folder in project.json
that doesn’t contain any files …
"content": [
"Views",
"wwwroot",
"logs"
],
(logs
in this case is an empty folder) … the published output doesn’t include the folder …
If I put a file in the logs
folder (test.txt
in this case), it publishes the folder …
I don’t think it should work that way. If I specify an empty content
folder (or a series of nested empty folders), then I should get folders in the published output that match what I’m requesting.
Issue Analytics
- State:
- Created 8 years ago
- Reactions:2
- Comments:13 (5 by maintainers)
Top Results From Across the Web
Don't publish particular folder in ASP.NET
Old question, but I found if I mark the folder as hidden in Windows Explorer, it doesn't show/publish in your solution.
Read more >Self-Contained Single-File does not produce a single file
I have set it up to publish as a self-contained single-file. However, in the publish directory is the EXE file and four DLLs....
Read more >Publish Sections and Folders | Omni CMS Support
Just like pages and files, you can publish a folder to push its contents to your live ... If the file has unpublished...
Read more >Set Users' Site Roles - Tableau
This site role offers non-administrators the maximum level of content access. Connect to Tableau or external data in the browser, build and publish...
Read more >How file access works in shared drives
If you move a folder to a shared drive: All members of the shared drive can view the contents of the folder, including...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I just ran into the same problem with todays dotnet core tooling. Any folder not created prior to dotnet publish call will not be published. My case is that I have prepublish tasks running that generate some files, but these files are not published due to the folders did not exists prior to calling dotnet publish.
The team is actively working on enabling MSBuild and the component affected will be superseded by the new project system, so I am closing this issue.