Skip to content

Commit 6993c96

Browse files
authored
Passing properties to the dotnet run command works. (#51285)
It's also listed as a valid argument further down on this page: 9b0663a
1 parent d41aa71 commit 6993c96

1 file changed

Lines changed: 1 addition & 3 deletions

File tree

docs/core/tools/dotnet-run.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,7 @@ dotnet run [<applicationArguments>]
2121
[-f|--framework <FRAMEWORK>] [--force] [--interactive]
2222
[-lp|--launch-profile <NAME>] [--no-build] [--no-cache]
2323
[--no-dependencies] [--no-launch-profile] [--no-restore] [--os <OS>]
24+
[-p|--property:<PROPERTYNAME>=<VALUE>]
2425
[--project <PATH>] [-r|--runtime <RUNTIME_IDENTIFIER>]
2526
[--sc|--self-contained] [--tl:[auto|on|off]] [-v|--verbosity <LEVEL>]
2627
[[--] [application arguments]]
@@ -32,9 +33,6 @@ dotnet run -h|--help
3233

3334
The `dotnet run` command provides a convenient option to run your application from the source code with one command. It's useful for fast iterative development from the command line. The command depends on the [`dotnet build`](dotnet-build.md) command to build the code. Any requirements for the build apply to `dotnet run` as well.
3435

35-
> [!NOTE]
36-
> `dotnet run` doesn't respect arguments like `/property:property=value`, which are respected by `dotnet build`.
37-
3836
Output files are written into the default location, which is `bin/<configuration>/<target>`. For example if you have a `netcoreapp2.1` application and you run `dotnet run`, the output is placed in `bin/Debug/netcoreapp2.1`. Files are overwritten as needed. Temporary files are placed in the `obj` directory.
3937

4038
If the project specifies multiple frameworks, executing `dotnet run` results in an error unless the `-f|--framework <FRAMEWORK>` option is used to specify the framework.

0 commit comments

Comments
 (0)