5 ms·
We don't have single binary releases, but we do have single folder releases that are guaranteed to work out of the box on any given windows server. For me, the
by bob1029 5y ago
We don't have single binary releases, but we do have single folder releases that are guaranteed to work out of the box on any given windows server. For me, the number of actual files is not of consequence. Just being able to run something and know its going to run is the key bit.
The new Self-Contained Deployments feature in .NET made our lives infinitely easier as a B2B software vendor. We no longer have to have sweaty-hands conversations with the customer about which .net frameworks are installed or even allowed (?!) in their environments. I literally click my mouse... 4 times in visual studio and have a zip file containing everything we need to send to the customer.
We also moved to SQLite recently, so that one zip file is literally the entire kingdom. You could grab a blank VM from Azure and our product would startup and run on it without any extra bullshit.
- blub 5y agoI'm surprised that this is now possible with .NET. It's amazing what Microsoft can achieve in 20 years if they put their hearts and souls into it.
- tonyedgecombe 5y agoI'm reminded of Joel Spolsky's request for this: https://www.joelonsoftware.com/2004/01/28/please-sir-may-i-have-a-linker/ https://www.joelonsoftware.com/2004/01/28/please-sir-may-i-h...
- stronglikedan 5y agoIs this the same approach as portable apps?
- ripley12 5y agoThere's something nice about the ergonomics of a single file compared to a single folder though. A single file is trivial to distribute as-is; you don't even need to put it in an archive. You can put multiple single-file apps in a directory on your PATH, no futzing with symlinks etc. There are certainly tradeoffs involved and it's not always the right decision, but these days I usually try to publish software as a single file until I can't.
- ziml77 5y agoNeXTSTEP and (through its lineage) macOS got it right. You put your executable and data files into a directory with a specific structure and then to the user it operates as if it's a single file. You get the benefits of a single folder distribution with the ergonomics of a single file distribution.
- seba_dos1 5y agoWhat happens if you try to, say, send that executable as an e-mail attachment?
- derefr 5y agoWell, first of all, you don't do that, because what email server anywhere is going to accept mail with an executable attached, without thinking it's some kind of attack? But in general, you put it in an archive. (Yes, that's inconvenient; but when you're coming from an OS where you already had to do that — e.g. macOS 9, where you had to use StuffIt Expander to distribute executables in order to ensure they retain their resource forks — switching from StuffIt to zip was a wash.) These OSes (NeXTStep, macOS) usually integrate some support for mounting disk images, though, and so executables packaged for distribution are usually packaged by putting them in a disk-image. To further decrease the friction (i.e. avoid having to say "copy this thing out of this directory into your /Applications dir", they usually make it so that if you run the app from inside the image, it copies itself to your /Applications dir, and then relaunches from there. Sometimes it even unmounts the image when it does that. Given that most people get programs from websites, though, there are also special techniques built into web browsers to make downloading executables on these OSes more transparent and less requiring the abstraction of a disk-image. E.g. Apple's https://en.wikipedia.org/wiki/.XIP https://en.wikipedia.org/wiki/.XIP format, where any .XIP downloaded in Safari will be automatically+transparently integrity-verified and unpacked, with the result being that it seems like you just "downloaded a folder" somehow.
- bob1029 5y ago> There's something nice about the ergonomics of a single file compared to a single folder though Agreed. We are going to move to proper single file (or as close as we can get) as soon as any sort of meaningful AOT compilation is available: https://github.com/dotnet/runtimelab/tree/feature/NativeAOT https://github.com/dotnet/runtimelab/tree/feature/NativeAOT https://github.com/dotnet/runtimelab/issues/248 https://github.com/dotnet/runtimelab/issues/248 There is a "PublishSingleFile" option, but that is just a zip file in disguise.
- gameswithgo 5y agoYep, that is good enough. What makes Linux so horrible of an experience for many desktop users is so much of the software is built with a server mindset, with a vast array of dynamic linking that often does not work. If the software is an up to date part of your particular distro's package manager, great. But when it isn't, total nightmare. And your end user desktop application just doesn't need to be built that way!
- beardog 5y agoFor people who aren't in the know about modern dotnet, you can also do single file deployment on top of the self contained deployment. There's even a ReadyToRun thing that precompiles things that would otherwise be JIT compiled. Experimenting with Uno framework, I was able to build a Skia Linux GUI that built to only 2 files, the program and a skia library.