cs-script VS dotnet-script

CS-Script

:: Querying AUR... Repository : aur Name : cs-script Keywords : None Version : 3.28.4.0-1 Description : Run C# sources like scripts URL : https://github.com/oleg-shilo/cs-script AUR URL : https://aur.archlinux.org/packages/cs-script Groups : None Licenses : MIT Provides : None Depends On : mono Make Deps : None Check Deps : None Optional Deps : None Conflicts With : None Maintainer : clofresh Votes : 0 Popularity : 0.000000 First Submitted : Sat 12 Nov 2016 01:56:26 PM GMT Last Modified : Sat 09 Jun 2018 05:18:39 AM BST Out-of-date : No

I did something like that in a pure C# game engine using this tool: https://github.com/oleg-shilo/cs-script/wiki

That said, there are some projects like cs-script that provide tools that let you treat C# more like a scripting language and omit that infrastructure. It's just not as feasible or useful as you start to write more complicated application types.

There are third party projects that support this: https://github.com/oleg-shilo/cs-script

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.