PublishSingleFile should have verb option for publish
See original GitHub issuedotnet publish
should accept a --single-file
option to be translated to -p:PublishSingleFile=True
.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:15 (15 by maintainers)
Top Results From Across the Web
Create a single file for application deployment - .NET
Choose Save to save the settings and return to the Publish dialog. Choose Publish to publish your app as a single file.
Read more >Use implicit RID for Publish Properties #26028 - dotnet/sdk
It would enable producing self contained apps, but only for the publish verb, just like the other Publish* properties. We should add:.
Read more >.NET Core: Separate .exe from other libraries when ...
1 Answer. If there is no constraint to use the framework-dependent publishing option you can publish with the PublishSingleFile option being ...
Read more >Publishing a self-contained single-file .NET 5 executable
In .NET Core 3.x the PublishSingleFile option also bundled native binaries. The IncludeNativeLibrariesForSelfExtract option is new wih .NET 5, ...
Read more >How to publish .NET console app to single independent . ...
PublishSingleFile - Enables single-file publishing. SelfContained - Determines whether the app will be self-contained or framework-dependent. " ...
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 FreeTop 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
Top GitHub Comments
I think adding those as well would make sense. It’s just as easy to add one as three.
Me and @KathleenDollard just discussed this and due to the finality of this change (we can’t really take it back) and the potential to lead to very confusing contents in your publish output, we would like to post-pone this change to 5.0, when we hopefully can address the publish incrementality issues.
We will pay attention to feedback meanwhile.