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 publish no-build switch disappeared
See original GitHub issueSteps to reproduce
Dotnet publish -no-build
Expected behavior
It is supported
Actual behavior
No longer supported
Environment data
dotnet --info output:
This is a useful switch. We would like to understand why it’s removed and if there is a replacement.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:18
- Comments:48 (25 by maintainers)
Top Results From Across the Web
Dotnet publish no-build switch disappeared · Issue #7521
Just got here looking for this. Trying to run dotnet publish with visual studio open breaks hard. Using --no-build would work. Incremental build ......
Read more >dotnet publish command - .NET CLI
dotnet publish - Publishes the application and its dependencies to a folder for deployment to a hosting system.
Read more >Dotnet publish looking for dependency in Debug directory ...
This property can be set in a publish profile, or is set dynamically by MSBuild during the build step. I haven't delved too...
Read more >dotnet publish switch error
Tried to run: dotnet publish "$tmp_server_dir/Arrowgene.Ddon.Cli/Arrowgene.Ddon. ... MSBUILD : error MSB1001: Unknown switch.
Read more >Building, running, publishing a asp.net core ...
Am I missing something really obvious with dotnet run? Simple to reproduce, just create an asp.net core app (.net framework) and add a...
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
Thanks all for the feedback. As I mentioned above, I’m in strong agreement on this. We will add --no-build in v2.1.0.
Whatever the solution will be, it seems clear from the comments above that Build -> Test -> Publish is a highly desired workflow, for myself included. Thus, a publish command that can take pre-existing output is a highly desirable requirement, whether this is a --no-build flag or some equivalent. Even more so using a hosted build agent service where build time = money.