runfile.win-x64
v1.0.0-alphaPre-release
Any Framework
Run C# code from remote locations using: dnx runfile [host/]owner/repo[@ref][:path]
Published
Nov 16, 2025
11mo ago
Total Downloads
1.7K
1,688
Install
dotnet add package runfile.win-x64 --version 1.0.0-alpha
No framework information available.
README
Run C# code programs from git repos on GitHub, GitLab and Azure DevOps.
Usage:
[dnx] runfile [--aot] [--alias ALIAS] <repoRef> [<appArgs>...]
Arguments:
<REPO_REF> Reference to remote file to run, with format [host/]owner/repo[@ref][:path]
host optional host name ([gist.]github.com|gitlab.com|dev.azure.com, default: github.com)
@ref optional branch, tag, or commit (default: default branch)
:path optional path to file in repo (default: program.cs at repo root)
Examples:
* kzu/[email protected]:run.cs (implied host github.com, explicit tag and file path)
* gitlab.com/kzu/sandbox@main:run.cs (all explicit parts)
* kzu/sandbox (implied host github.com, ref and path defaults)
Can be an alias previously set with --alias.
<appArgs> Arguments passed to the C# program that is being run.
Options:
--aot (optional) Enable dotnet AOT defaults for run file.cs. Defaults to false.
--alias ALIAS (optional) Assign an alias on first usage which can be used instead of the full ref.
Example:
dnx runfile kzu/runfile@v1:run.cs dotnet rocks
View source:
#:package Spectre.Console@*
using Spectre.Console;
AnsiConsole.MarkupLine($"Hello world from [green]dnx[/] [yellow]gist[/] :rocket: [bold italic]{string.Join(' ', args)}[/]");
The repo does not need to be public. In that case, the same authentication used by your local
gitwill be used to access the file, via the Git Credential Manager.
When running different files from the same repo+ref, the download will be performed only once. The last download etag is used to avoid downloading on each run.
Sponsors
Adoption Assessment
Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.
This version is marked prerelease. Validate its API and upgrade path before production use.No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.No target framework metadata is available. Confirm compatibility in a representative project before standardising on this package.
Related Guides & Workflows
Learn how to evaluate, integrate, or audit this package in your .NET project.