Our great sponsors
-
ClearScript
A library for adding scripting to .NET applications. Supports V8 (Windows, Linux, macOS) and JScript/VBScript (Windows).
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
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.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
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
I personally use Bullseye and SimpleExec instead of Nuke. I really like sticking to "normal" C#. I used Cake before but never liked it.
I personally use Bullseye and SimpleExec instead of Nuke. I really like sticking to "normal" C#. I used Cake before but never liked it.
[1] http://scriptcs.net/