8000 Update multi-file 'dotnet run file' documentation by jjonescz · Pull Request #48437 · dotnet/sdk · GitHub
[go: up one dir, main page]

Skip to content

Update multi-file 'dotnet run file' documentation #48437

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 22 commits into from
May 7, 2025
Merged
Changes from 1 commit
Commits
Show all changes
22 commits
Select commit Hold shift + click to select a range
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
Prev Previous commit
Next Next commit
Clarify target directory
  • Loading branch information
jjonescz committed Apr 16, 2025
commit 72eca2c3d035e4a5ae71ee4c512b44cbf69b33ab
3 changes: 2 additions & 1 deletion documentation/general/dotnet-run-file.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,7 @@ dotnet project convert

The path passed to `dotnet run ./some/path.cs` is called *the target path*.
The target path must be a file which has the `.cs` file extension, but we could allow folders as well in the future.
*The target directory* is the directory of the target file.

We can consider adding an option like `dotnet run --cs-from-stdin` which would read the C# file from the standard input
(or `dotnet run -` although then it's unclear which programming language the input is in)
Expand Down Expand Up @@ -135,7 +136,7 @@ That's because it might be perfectly reasonable to have file-based programs nest

### Multiple entry points

If there are multiple entry-point files in the target directory, the build ignores other entry-point files.
If there are multiple entry-point files in the target directory subtree, the build ignores other entry-point files.

Thanks to this, it is possible to have a structure like
```
Expand Down
0