Skip to content

Commit 23801e6

Browse files
committed
Add info about FDD lookups
1 parent 25dc695 commit 23801e6

File tree

1 file changed

+16
-1
lines changed

1 file changed

+16
-1
lines changed

docs/core/deploying/index.md

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -111,7 +111,7 @@ The following table provides quick examples of how to publish your app.
111111
| [ReadyToRun deployment](#readytorun-deployment) | `dotnet publish -c Release [-r <RID>] -p:PublishReadyToRun=true` |
112112

113113
::: zone-end
114-
114+
[](#framework-dependent-deployment)
115115
## Framework-dependent deployment
116116

117117
Framework-dependent deployment is the default mode when you publish from either the CLI or Visual Studio. In this mode, a platform-specific executable host is created to host your cross-platform app. The host executable filename varies per platform and is named something similar to `<PROJECT-FILE>.exe`. You can run this executable directly instead of calling `dotnet <PROJECT-FILE>.dll`, which is still an acceptable way to run the app.
@@ -167,6 +167,21 @@ This switch explicitly tells the .NET SDK to create a framework-dependent deploy
167167

168168
::: zone-end
169169

170+
### Configure .NET install search behavior
171+
172+
In .NET 9 and later versions, you can configure the .NET installation search paths of the published executable via the [`AppHostDotNetSearch`](../project-sdk//msbuild-props.md#apphostdotnetsearch) and [`AppHostRelativeDotNet`](../project-sdk//msbuild-props.md#apphostrelativedotnet) properties.
173+
174+
`AppHostDotNetSearch` allows specifying one or more locations where the executable will look for a .NET installation:
175+
176+
- `AppLocal`: app executable's folder
177+
- `AppRelative`: path relative to the app executable
178+
- `EnvironmentVariable`: value of [`DOTNET_ROOT[_<arch>]`](../tools/dotnet-environment-variables.md#dotnet_root-dotnet_rootx86-dotnet_root_x86-dotnet_root_x64) environment variables
179+
- `Global`: [registered](https://github.com/dotnet/designs/blob/main/accepted/2020/install-locations.md#global-install-to-custom-location) and [default](https://github.com/dotnet/designs/blob/main/accepted/2020/install-locations.md#global-install-to-default-location) global install locations
180+
181+
`AppHostRelativeDotNet` specifies the path relative to the executable that will be searched when `AppHostDotNetSearch` contains `AppRelative`.
182+
183+
For more information, see [`AppHostDotNetSearch`](../project-sdk//msbuild-props.md#apphostdotnetsearch), [`AppHostRelativeDotNet`](../project-sdk//msbuild-props.md#apphostrelativedotnet) and [install location options in apphost](https://github.com/dotnet/designs/blob/main/proposed/apphost-embed-install-location.md).
184+
170185
### Cross-platform DLL deployment
171186

172187
Alternatively, you can publish your app as a cross-platform DLL without a platform-specific executable. In this mode, a `<PROJECT-NAME>.dll` file is created in the publish output folder. To run your app, navigate to the output folder and use the `dotnet <PROJECT-NAME>.dll` command.

0 commit comments

Comments
 (0)