You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -93,7 +93,7 @@ Running `dotnet build` is equivalent to running `dotnet msbuild -restore`; howev
93
93
94
94
Forces all dependencies to be resolved even if the last restore was successful. Specifying this flag is the same as deleting the *project.assets.json* file.
@@ -121,7 +121,7 @@ Running `dotnet build` is equivalent to running `dotnet msbuild -restore`; howev
121
121
122
122
If you specify the `--output` option when running this command on a solution, the CLI will emit a warning (an error in 7.0.200) due to the unclear semantics of the output path. The `--output` option is disallowed because all outputs of all built projects would be copied into the specified directory, which isn't compatible with multi-targeted projects, as well as projects that have different versions of direct and transitive dependencies. For more information, see [Solution-level `--output` option no longer valid for build-related commands](../compatibility/sdk/7.0/solution-level-output-no-longer-valid.md).
123
123
124
-
[!INCLUDE [os](../../../includes/cli-os.md)]
124
+
-[!INCLUDE [os](../../../includes/cli-os.md)]
125
125
126
126
-**`-p|--property:<PROPERTYNAME>=<VALUE>`**
127
127
@@ -136,23 +136,23 @@ Running `dotnet build` is equivalent to running `dotnet msbuild -restore`; howev
136
136
137
137
Specifies the target runtime. For a list of Runtime Identifiers (RIDs), see the [RID catalog](../rid-catalog.md). If you use this option with .NET 6 SDK, use `--self-contained` or `--no-self-contained` also. If not specified, the default is to build for the current OS and architecture.
Sets the value of the `$(VersionSuffix)` property to use when building the project. This only works if the `$(Version)` property isn't set. Then, `$(Version)` is set to the `$(VersionPrefix)` combined with the `$(VersionSuffix)`, separated by a dash.
The [framework](../../standard/frameworks.md) that was specified at build time. The framework must be defined in the [project file](../project-sdk/overview.md). If you specified the framework at build time, you must specify the framework when cleaning.
@@ -62,9 +62,9 @@ The `dotnet clean` command cleans the output of the previous build. It's impleme
62
62
63
63
Cleans the output folder of the specified runtime. This is used when a [self-contained deployment](../deploying/index.md#self-contained-deployment) was created.
Copy file name to clipboardExpand all lines: docs/core/tools/dotnet-new-details.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,15 +36,13 @@ If the package is installed locally or is found on the official NuGet website, i
36
36
By default, `dotnet new details` uses the hierarchy of NuGet configuration files from the current directory to determine the NuGet source the package can be installed from. If `--nuget-source` is specified, the source is added to the list of sources to be checked.
37
37
To check the configured sources for the current directory use [`dotnet nuget list source`](dotnet-nuget-list-source.md). For more information, see [Common NuGet Configurations](/nuget/consume-packages/configuring-nuget-behavior).
Copy file name to clipboardExpand all lines: docs/core/tools/dotnet-new-install.md
+3-7Lines changed: 3 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,15 +70,11 @@ Starting with .NET SDK 6.0.100, installed template packages are available in lat
70
70
71
71
Allows installing template packages from the specified sources even if they would override a template package from another source. Available since .NET SDK 7.0.100.
0 commit comments