With .NET 10, you now have no excuse not to start a collection of utility scripts that call into application code.

Atomic Object is a software consultancy specializing in custom software development and product design. Readers can learn about software development methodologies, user-centered design principles, and agile practices. With case studies, blog posts, and technical insights, Atomic Object provides  guidance and expertise for building innovative and user-friendly software products.

Atomic Spin

.NET 10 introduces file-based apps, enabling C# developers to run standalone .cs files directly with `dotnet run file.cs` — no .csproj required. Scripts can reference NuGet packages and existing project files via directives like `#:package` and `#:project`, giving scripts direct access to application domain logic. This fills a long-standing gap in the C# ecosystem (previously addressed only by F#'s `dotnet fsi` or third-party tools), making it practical to maintain a Scripts/ folder for data seeding, format verification, one-off exports, and other utility tasks without creating throwaway console apps or polluting test suites.

C# Finally Has First-Class CLI Scripts in .NET 10

<p>Great article, I wasn’t aware of this feature. Will give this a go!</p>


<p>Very specific one-of-a-kind requirement. Nothing to see here, move along.</p>
