Publishing doesn't publish modified Views when compilation is skipped
See original GitHub issueIf I modify a View manually (and that’s all I do), then perform a dotnet publish
, the modified View is not moved into the published output. Therefore, a deployment will deploy a stale View. This one is easy to repro: Just mod a View file and do nothing else, re-publish … you will get …
Project www_XXXXX_com (.NETStandardApp,Version=v1.5) was previously compiled.
Skipping compilation.
… check the published output. The View you modded will not get published to the output.
[EDIT] This prob also applies to any content
file that is modified.
Issue Analytics
- State:
- Created 8 years ago
- Comments:14 (11 by maintainers)
Top Results From Across the Web
Sitecore is skipping items during publishing. How to ...
Go to the item in Content Editor and on the Publish tab, click Change in the restrictions section. Click the Targets tab. On...
Read more >Publishing is skipped [closed]
There is a stage publishing target. I have published to Stage Database many times in the past (incremental, smart, all republish) and there...
Read more >`skip in publish` · Issue #3136 · sbt/sbt
I propose that we implement a flag named skip in publish to mark a subproject as non-publishing. steps skip in publish := true...
Read more >Visual Studio publish profiles (.pubxml) for ASP.NET Core ...
Learn how to create publish profiles in Visual Studio and use them for managing ASP.NET Core app deployments to various targets.
Read more >Release pipelines and artifact sources - Azure
By default, build artifacts are downloaded to the agent running the pipeline. You can also configure a step in your stage to skip...
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
Solved by adding back
.UseContentRoot(Directory.GetCurrentDirectory())
toWebHostBuilder
. Never take that off there you silly green dino!Thanks @davidfowl – Truly, one of the greatest.
Might be a problem after all: https://github.com/dotnet/cli/issues/2989