dotnet-script VS AutoUpdater.NET

Especially because these languages are only one package/install away and not two. I don‘t really get for which audience is targeted here. Usage in JS projects maybe, but then why not write it as npm tasks. ..

I‘m playing around with dotnet-scripts [1] at the moment (C# shop mainly) and this has the same issue imho. The reason why I looked into it was because we have developers not accustomed to bash etc. I still find it silly and would rather use ruby so…

[1] https://github.com/dotnet-script/dotnet-script

>making powershell actually enjoyable to use

My solution was to stop using it and instead use dotnet-script

https://github.com/dotnet-script/dotnet-script

Scripting with the full power of modern C# has been a huge win for me. And same/similar scripts will work on Windows/Linux/Mac. As my work language is C#, I don't have to context switch to another language for scripting.

I usually create a container that has all database migrations and tool to execute those migrations. I name migrations as [yyyyMMdd-HHmm-migration-name.sql] but please feel free to use any naming scheme, keep in mind how the tool would order multiple files to run those migrations. I have also added a wait-for-db.csx file that I would use as the entry point for database migrations container. This is a dotnet-script file and would be run using dotnet-script. I have pinned the versions that are compatible with .net sdk 3.1 as this the version roundhouse is build against at the time of writing.

thanks, this is very good idea too, and with dotnet-script we can publish executable out of the script!

It sounds like this is feedback for the author of the dotnet script tool: https://github.com/dotnet-script/dotnet-script

Yes, you can have single-file scripts too. There might be more options to achieve this, but the one that I use is running *.csx files via the dotnet-script (https://github.com/dotnet-script/dotnet-script).

I do agree.

I think .Net has got it right. And dotnet-script [https://github.com/dotnet-script/dotnet-script] has been a game-changer for me with a REPL-like experience for unit testing and writing command-line utilities.

It's not a website, it's a project.

You could also maybe check out AutoUpdater.NET as another possibility.

Aa others mentioned, it just more common to have an auto-updater mechanism built-in in your app. Check out AutoUpdater.NET which periodically check the server for new versions, download it in background and allow you to present a "update ready" button to the user that quickly restart the app to the new version when they are ready to apply it. A bit like the Chrome or Discord update ready buttons.

Good catch. Hmm, looks like Squirrel might be a no go. Oh well. My examples were not heavily researched. Just something to point in a starter direction. At a glance this looks promising too: https://github.com/ravibpatel/AutoUpdater.NET

Libraries like https://github.com/ravibpatel/AutoUpdater.NET, and plenty of others. This may not fit your needs, but maybe it does.

But it AutoUpdater.NET(https://github.com/ravibpatel/AutoUpdater.NET) does quite the same. It only looks at your own server instead of github. You should be able to get an idea of how it works and how to implement it using github instead.

I have a few desktop apps that uses AutoUpdater.NET to update the app on startup, as well as one app that's linked to a mapped drive. Since both apps are self-contained, it's always been a pain to update them - you either have to copy the entire 150 MB publish directory to your update location, or you have to pick and choose which binaries were updated, which you'd then push into a ZIP folder.