8000 Improve documentation to answer #664 by maximetinu · Pull Request #665 · dotnet-script/dotnet-script · GitHub
[go: up one dir, main page]

Skip to content

Improve documentation to answer #664 #665

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 21, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 11 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,14 @@ Instead of `main.csx` which is the default, we now have a file named `custom.csx

### Running scripts

Scripts can be executed directly from the shell as if they were executables.
You can execute your script using **dotnet script** or **dotnet-script**.

```bash
dotnet script foo.csx
dotnet-script foo.csx
```

On OSX/Linux, scripts can be executed directly from a shell as if they were executables.

```bash
foo.csx arg1 arg2 arg3
Expand All @@ -164,7 +171,9 @@ The OSX/Linux shebang directive should be **#!/usr/bin/env dotnet-script**
Console.WriteLine("Hello world");
```

You can execute your script using **dotnet script** or **dotnet-script**, which allows you to pass arguments to control your script execution more.
On Windows, you can run **dotnet register script** to achieve a similar behaviour. This register dotnet-script in the Windows registry as the tool to process .csx files.

You can pass arguments to control your script execution more.

```bash
foo.csx arg1 arg2 arg3
Expand Down
0