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
Copy file name to clipboardExpand all lines: docs/core/tools/dotnet-environment-variables.md
+1-5Lines changed: 1 addition & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.date: 11/08/2023
6
6
7
7
# .NET environment variables
8
8
9
-
**This article applies to:** ✔️ .NET Core 3.1 SDK and later versions
9
+
**This article applies to:** ✔️ .NET 6 SDK and later versions
10
10
11
11
In this article, you'll learn about the environment variables used by .NET. Some environment variables are used by the .NET runtime, while others are only used by the .NET SDK and .NET CLI. Some environment variables are used by all three components.
12
12
@@ -304,10 +304,6 @@ If set to `1` (enabled), enables rolling forward to a pre-release version from a
304
304
305
305
For more information, see [the `--roll-forward` option for the `dotnet` command](dotnet.md#rollforward).
306
306
307
-
### `DOTNET_ROLL_FORWARD_ON_NO_CANDIDATE_FX`
308
-
309
-
Disables minor version roll forward, if set to `0`. This setting is superseded in .NET Core 3.0 by `DOTNET_ROLL_FORWARD`. The new settings should be used instead.
310
-
311
307
### `DOTNET_CLI_FORCE_UTF8_ENCODING`
312
308
313
309
Forces the use of UTF-8 encoding in the console, even for older versions of Windows 10 that don't fully support UTF-8. For more information, see [SDK no longer changes console encoding when finished](../compatibility/sdk/8.0/console-encoding-fix.md).
Copy file name to clipboardExpand all lines: docs/core/tools/dotnet-new.md
+4-9Lines changed: 4 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,11 +2,11 @@
2
2
title: dotnet new <TEMPLATE>
3
3
description: The dotnet new command creates new .NET projects based on the specified template.
4
4
no-loc: [Blazor, WebAssembly]
5
-
ms.date: 02/15/2024
5
+
ms.date: 10/28/2025
6
6
---
7
7
# dotnet new <TEMPLATE>
8
8
9
-
**This article applies to:** ✔️ .NET Core 3.1 SDK and later versions
9
+
**This article applies to:** ✔️ .NET 6 SDK and later versions
10
10
11
11
## Name
12
12
@@ -49,20 +49,15 @@ To activate tab completion for the .NET SDK, see [Enable tab completion](enable-
49
49
50
50
You can run [`dotnet new list`](dotnet-new-list.md) to see a list of all installed templates.
51
51
52
-
Starting with .NET Core 3.0 SDK and ending with .NET SDK 5.0.300, the CLI searches for templates in NuGet.org when you invoke the `dotnet new` command in the following conditions:
53
-
54
-
- If the CLI can't find a template match when invoking `dotnet new`, not even partial.
55
-
- If there's a newer version of the template available. In this case, the project or artifact is created but the CLI warns you about an updated version of the template.
56
-
57
-
Starting with .NET SDK 5.0.300, the [`search` command](dotnet-new-search.md) should be used to search for templates in NuGet.org.
52
+
The [`search` command](dotnet-new-search.md) should be used to search for templates in NuGet.org.
58
53
59
54
For a list of templates that ship with the .NET SDK, see [Preinstalled templates](dotnet-new-sdk-templates.md#preinstalled-templates).
60
55
61
56
## Options
62
57
63
58
-**`--dry-run`**
64
59
65
-
Displays a summary of what would happen if the given command were run if it would result in a template creation. Available since .NET Core 2.2 SDK.
60
+
Displays a summary of what would happen if the given command were run if it would result in a template creation.
0 commit comments