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/install/linux-scripted-manual.md
+12-4Lines changed: 12 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -131,7 +131,9 @@ Different versions of .NET can be extracted to the same folder, which coexist si
131
131
132
132
### Example
133
133
134
-
The following commands set the environment variable `DOTNET_ROOT` to the current working directory followed by `.dotnet`. They then create the directory if it doesn't exist and extract the contents of the file specified by the `DOTNET_FILE` environment variable to the `.dotnet` directory. Both the `.dotnet` directory and its `tools` subdirectory are added to the `PATH` environment variable.
134
+
<!-- Note, this content is copied in macos.md. Any fixes should be applied there too, though content may be different -->
135
+
136
+
The following commands use Bash to set the environment variable `DOTNET_ROOT` to the current working directory followed by `.dotnet`. That directory is created if it doesn't exist. The `DOTNET_FILE` environment variable is the filename of the .NET binary release you want to install. This file is extracted to the `DOTNET_ROOT` directory. Both the `DOTNET_ROOT` directory and its `tools` subdirectory are added to the `PATH` environment variable.
135
137
136
138
> [!IMPORTANT]
137
139
> If you run these commands, remember to change the `DOTNET_FILE` value to the name of the .NET binary you downloaded.
The preceding install script approach allows installing different versions into separate locations so you can choose explicitly which one to use by which app. However, you can still install multiple versions of .NET to the same folder.
150
+
You can install more than one version of .NET in the same folder.
151
+
152
+
You can also install .NET to the home directory identified by the `HOME` variable or `~` path:
153
+
154
+
```bash
155
+
export DOTNET_ROOT=$HOME/.dotnet
156
+
```
149
157
150
158
## Verify downloaded binaries
151
159
@@ -157,7 +165,7 @@ The preceding install script approach allows installing different versions into
157
165
158
166
If you used the previous install script, the variables set only apply to your current terminal session. Add them to your shell profile. There are many different shells available for Linux and each has a different profile. For example:
159
167
160
-
-**Bash Shell**: *~/.bash_profile*,*~/.bashrc*
168
+
-**Bash Shell**: *~/.bash_profile* or*~/.bashrc*
161
169
-**Korn Shell**: *~/.kshrc* or *.profile*
162
170
-**Z Shell**: *~/.zshrc* or *.zprofile*
163
171
@@ -173,7 +181,7 @@ Set the following two environment variables in your shell profile:
173
181
174
182
-`PATH`
175
183
176
-
This variable should include both the `DOTNET_ROOT` folder and the user's _.dotnet/tools_ folder:
184
+
This variable should include both the `DOTNET_ROOT` folder and the `DOTNET_ROOT/tools` folder:
Copy file name to clipboardExpand all lines: docs/core/install/macos-notarization-issues.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ Beginning with macOS Catalina (version 10.15), all software built after June 1,
12
12
13
13
## Installing .NET
14
14
15
-
The installers for .NET (both runtime and SDK) have been notarized since February 18, 2020. Prior released versions aren't notarized. You can manually install a non-notarized version of .NET by first downloading the installer, and then using the `sudo installer` command. For more information, see [Download and manually install for macOS](./macos.md#download-and-manually-install).
15
+
The installers for .NET (both runtime and SDK) have been notarized since February 18, 2020. Prior released versions aren't notarized. You can manually install a non-notarized version of .NET by first downloading the installer, and then using the `sudo installer` command. For more information, see [Download and manually install for macOS](./macos.md#manual-install).
<!-- Note, this content is taken from linux-scripted-manual.md but changed for macOS. Any fixes should be applied there too, though content may be different -->
95
95
96
96
As an alternative to the macOS installers for .NET, you can download and manually install the SDK and runtime. Manual installation is usually performed as part of continuous integration testing. For a developer or user, it's generally better to use an [installer](https://dotnet.microsoft.com/download/dotnet).
97
97
98
-
First, download a **binary** release for either the SDK or the runtime from one of the following sites. If you install the .NET SDK, you won't need to install the corresponding runtime:
98
+
Download a **binary** release for either the SDK or the runtime from one of the following sites. The .NET SDK includes the corresponding runtime:
Next, extract the downloaded file and use the `export` command to set `DOTNET_ROOT` to the extracted folder's location and then ensure .NET is in PATH. This should make the .NET CLI commands available at the terminal. For more information about .NET environment variables, see [.NET SDK and CLI environment variables](../tools/dotnet-environment-variables.md#net-sdk-and-cli-environment-variables).
105
+
Extract the downloaded file and use the `export` command to set `DOTNET_ROOT` to the extracted folder's location and then ensure .NET is in PATH. Exporting `DOTNET_ROOT` makes the .NET CLI commands available in the terminal. For more information about .NET environment variables, see [.NET SDK and CLI environment variables](../tools/dotnet-environment-variables.md#net-sdk-and-cli-environment-variables).
106
106
107
-
Alternatively, after downloading the .NET binary, the following commands can be run from the directory where the file is saved to extract the runtime. These commands also make the .NET CLI commands available at the terminal and set the required environment variables. **Remember to change the `DOTNET_FILE` value to the name of the downloaded binary**:
107
+
Different versions of .NET can be extracted to the same folder, which coexist side-by-side.
108
+
109
+
### Example
110
+
111
+
The following commands use Bash to set the environment variable `DOTNET_ROOT` to the current working directory followed by `.dotnet`. That directory is created if it doesn't exist. The `DOTNET_FILE` environment variable is the filename of the .NET binary release you want to install. This file is extracted to the `DOTNET_ROOT` directory. Both the `DOTNET_ROOT` directory and its `tools` subdirectory are added to the `PATH` environment variable.
112
+
113
+
> [!IMPORTANT]
114
+
> If you run these commands, remember to change the `DOTNET_FILE` value to the name of the .NET binary you downloaded.
108
115
109
116
```bash
110
117
DOTNET_FILE=dotnet-sdk-8.0.100-osx-x64.tar.gz
111
-
export DOTNET_ROOT=$(pwd)/dotnet
118
+
export DOTNET_ROOT=$(pwd)/.dotnet
112
119
113
120
mkdir -p "$DOTNET_ROOT"&& tar zxf "$DOTNET_FILE" -C "$DOTNET_ROOT"
114
121
115
122
export PATH=$PATH:$DOTNET_ROOT
116
123
```
117
124
118
-
> [!TIP]
119
-
> The preceding `export` commands only make the .NET CLI commands available for the terminal session in which it was run.
120
-
>
121
-
> You can edit your shell profile to permanently add the commands. There are a number of different shells available for Linux and each has a different profile. For example:
122
-
>
123
-
> -**Bash Shell**: *~/.bash_profile*, *~/.bashrc*
124
-
> -**Korn Shell**: *~/.kshrc* or *.profile*
125
-
> -**Z Shell**: *~/.zshrc* or *.zprofile*
126
-
>
127
-
> Edit the appropriate source file for your shell and add `:$HOME/dotnet` to the end of the existing `PATH` statement. If no `PATH` statement is included, add a new line with `export PATH=$PATH:$HOME/dotnet`.
128
-
>
129
-
> Also, add `export DOTNET_ROOT=$HOME/dotnet` to the end of the file.
125
+
You can install more than one version of .NET in the same folder.
126
+
127
+
You can also install .NET to the home directory identified by the `HOME` variable or `~` path:
130
128
131
-
This approach lets you install different versions into separate locations and choose explicitly which one to use by which application.
If you used the instructions in the [Manual install example](#example) section, the variables set only apply to your current terminal session. Add them to your shell profile. There are many different shells available for macOS and each has a different profile. For example:
142
+
143
+
-**Bash Shell**: *~/.profile*, */etc/profile*
144
+
-**Korn Shell**: *~/.kshrc* or *.profile*
145
+
-**Z Shell**: *~/.zshrc* or *.zprofile*
146
+
147
+
Set the following two environment variables in your shell profile:
148
+
149
+
-`DOTNET_ROOT`
150
+
151
+
This variable is set to the folder .NET was installed to, such as `$HOME/.dotnet`:
152
+
153
+
```bash
154
+
export DOTNET_ROOT=$HOME/.dotnet
155
+
```
156
+
157
+
-`PATH`
158
+
159
+
This variable should include both the `DOTNET_ROOT` folder and the `DOTNET_ROOT/tools` folder:
160
+
161
+
```bash
162
+
export PATH=$PATH:$DOTNET_ROOT:$DOTNET_ROOT/tools
163
+
```
164
+
139
165
## Arm-based Macs
140
166
141
167
The following sections describe things you should consider when installing .NET on an Arm-based Mac.
Copy file name to clipboardExpand all lines: docs/core/runtime-discovery/troubleshoot-app-launch.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -240,15 +240,15 @@ For more information on installation using the script, see [Install with bash au
240
240
You can download a binary archive of .NET from the [download page](https://dotnet.microsoft.com/download/dotnet). From the **Binaries** column of the runtime download, download the binary release matching the required architecture. Extract the downloaded archive to the ".NET location" specified in the error message.
241
241
242
242
::: zone pivot="os-windows"
243
-
For more details on manual installation, see [Install .NET on Windows](../install/windows.md#install-with-powershell-automation)
243
+
For more information about manual installation, see [Install .NET on Windows](../install/windows.md#install-with-powershell-automation)
244
244
::: zone-end
245
245
246
246
::: zone pivot="os-linux"
247
-
For more details on manual installation, see [Install .NET on Linux](../install/linux.md#manual-installation)
247
+
For more information about manual installation, see [Install .NET on Linux](../install/linux.md#manual-installation)
248
248
::: zone-end
249
249
250
250
::: zone pivot="os-macos"
251
-
For more details on manual installation, see [Install .NET on macOS](../install/macos.md#download-and-manually-install)
251
+
For more information about manual installation, see [Install .NET on macOS](../install/macos.md#manual-install)
0 commit comments