InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now. Learn more →
Dotnet-script Alternatives
Similar projects and alternatives to dotnet-script
-
-
InfluxDB
InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.
-
-
-
winget-cli
WinGet is the Windows Package Manager. This project includes a CLI (Command Line Interface), PowerShell modules, and a COM (Component Object Model) API (Application Programming Interface).
-
-
Introducing .NET Multi-platform App UI (MAUI)
.NET MAUI is the .NET Multi-platform App UI, a framework for building native device applications spanning mobile, tablet, and desktop.
-
MySQL
MySQL Server, the world's most popular open source database, and MySQL Cluster, a real-time, open source transactional database.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
-
runtimelab
This repo is for experimentation and exploring new ideas that may or may not make it into the main dotnet/runtime repo.
-
interactive
.NET Interactive combines the power of .NET with many other languages to create notebooks, REPLs, and embedded coding experiences. Share code, explore data, write, and learn across your apps in ways you couldn't before.
-
-
-
CSharpRepl
A command line C# REPL with syntax highlighting – explore the language, libraries and nuget packages interactively.
-
-
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
dotnet-script discussion
dotnet-script reviews and mentions
-
Java in the Small
It should be able to! F# has "gradual typing" and full type inference which means you often do not need to specify the types at all, and it also happens to be whitespace-sensitive language much like Python is. Both of these aspects should make it feel quite familiar while also giving you full advantages of static typing.
One thing to note is I find `dotnet fsi {some script name}.fsx` taking more time to start than ideal - up to 800ms is just too much, normal .NET applications usually start in a fraction of this.
I recently posted a submission for "FSharpPacker" that lets you compile F# scripts to standalone applications (either runtime-dependent, self-contained or fully native binaries, much like Go), it also has some comments on getting the best mileage out of it: https://news.ycombinator.com/item?id=42304835
Probably the best feature that also comes with scripting (both C# and F#) is "inline" nuget references e.g. #r "nuget: FSharp.Control.TaskSeq" which will automatically pull the dependency from nuget without ever dealing with manually installing it or tinkering with build system in any other way.
Some additional links:
https://learn.microsoft.com/en-us/dotnet/fsharp/tools/fsharp...
https://github.com/dotnet-script/dotnet-script (C# is also a quite productive language for scripting and small programs because of top-level statements, record types, pattern matching and many other functional features though perhaps not as strongly represented as in F#)
https://github.com/waf/CSharpRepl
-
Jeffrey Snover and the Making of PowerShell
Adding packages is `dotnet add {PackageName}`. That's it.
Worrying about version compatibility for new projects has stopped being an issue long time ago. The package either targets NS2.0 or whatever latest LTS currently is, in which case you just add its reference, or it doesn't in which case you use something else.
If it does, in 98% situations it just works. In the last 2% it has native dependencies which means either a) the package ships with binaries build for all popular platforms, b) the package adds a platform-specific dependent package automatically, or manually and mentions that in README, or c) the package comes with windows only native dll, which is happens with ancient poorly maintained packages, it's a rare case nowadays but it does happen.
As someone whose primary PL is C#, I found https://github.com/waf/CSharpRepl and https://github.com/dotnet-script/dotnet-script far more accessible and useful. Compilation caching for the latter works relatively well to make startup latency tolerable.
Or I just do `dotnet new console -o MyScriptName --aot`, echo code into Program.cs and `dotnet publish -o .` it. Some do that with Rust as well. Especially useful if you need your script to go through a lot of data quickly and parallelize that well too.
- LINQPad – The .NET Programmer's Playground
-
Google ZX – A tool for writing better scripts
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
-
Simple PowerShell things allowing you to dig a bit deeper than usual
>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.
-
REST API using C# .NET 7 with MySql
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.
-
Is it possible to create executable from file instead of project, like java or go?
thanks, this is very good idea too, and with dotnet-script we can publish executable out of the script!
-
dotnet script script.cxs says no dotnet found
It sounds like this is feedback for the author of the dotnet script tool: https://github.com/dotnet-script/dotnet-script
- Administrative Scripting with Julia
-
C# vs Python
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).
-
A note from our sponsor - InfluxDB
www.influxdata.com | 21 May 2025
Stats
dotnet-script/dotnet-script is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of dotnet-script is C#.
Popular Comparisons
- dotnet-script VS csharplang
- dotnet-script VS cs-script
- dotnet-script VS omnisharp-vim
- dotnet-script VS .NET-Obfuscator
- dotnet-script VS ScriptCS
- dotnet-script VS RoslynPad
- dotnet-script VS Visual Studio Community
- dotnet-script VS AutoUpdater.NET
- dotnet-script VS Squirrel
- dotnet-script VS Kuinox.CSharpScript