"AfterPublish" doesn't invoked
See original GitHub issueDescribe the bug
ASP.Net Core project
To Reproduce
- download the Avalonia Gallery
- create a task that depends on “AfterPublish” task
dotnet publish
- “AfterPublish” and custom task doesn’t not invoked
- if it is a ASP.Net Core project, “AfterPublish” does be invoked.
Exceptions (if any)
both of the two tasks should be invoked
Further technical details
sdk: 6.0.300
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
AfterPublish target not working - msbuild
AfterPublish is called after Publish target, but Publish is not the target called when you publish a web application. Publish is the target...
Read more >Is there any msbuild target that is executed after publishing ...
I need to execute a command after publishing a .NET core WPF app in Visual Studio. I tried following custom target in .csproj...
Read more >[Solved]-AfterPublish script doesn't run when I publish a web ...
Coding example for the question AfterPublish script doesn't run when I publish a web ... invoke-command -scriptblock { &'$(ScriptLocation)' ...
Read more >workflow cannot be found. make sure that it is part of the ...
hello, I'm trying to invoke a workflow from a shared folder. it is giving me an error “workflow cannot be found. Make sure...
Read more >After Publish to machine with self signed certificate
If we publish a Asp.Net webproject to our development IIS Server which has an self signed certificate an message appears that you have...
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
the last stage of non-web project is
Publish
, so for now, the following workaround works for me.This one slipped through the cracks - I’ve added it to our triage bucket for discussion. As I stated above, I definitely believe that we need to do this work to enable consistent publish behavior for all project types, not just web projects. We’ll also need to consult with @vijayrkn and his team to make sure the VS/Web publish behavior isn’t impacted.