UpdatR VS dotnet-script

With top level statements a .cs-file can be quite similar to csx. I just whish I could specify the nuget packages in it so we could ditch the csproj. Or that csx for full support in dotnet run. I usually just use top level statements with Bullseye, that's quite neat even if it requires a csproj. Here's an example of what I do with it: https://github.com/OskarKlintrot/UpdatR/blob/main/tools/Build/Build.cs

My side project is UpdatR (https://github.com/OskarKlintrot/UpdatR) which I use to replace Nukeeper at work. Nukeeper is deprecated and stopped working on Azure DevOps but Dependabot isn't available on Azure DevOps. "How hard can it be" I thought and spent too many evenings getting it working good enough to actually use... It updates packages to the latest version that is still supported by the target framework and generates a title and body to be used in the PR. It seems to be working so far. I want it to support multitarget frameworks and updating Directory.Build.props too, which are no small tasks...

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.